hid_hw_stop(9)

okay so this is hid_hw_stop(9), straight out of the Kernel API Manual, and it’s giving “cleanup era” energy 💅✨

🌸 NAME 🌸

hid_hw_stop — stop underlying HW

✨ SYNOPSIS ✨

void hid_hw_stop (struct hid_device *hdev );

🎀 ARGUMENTS 🎀

• hdev — hid device. yes bestie, that’s the one 🫶

🦋 DESCRIPTION 🦋

okay so here’s the tea: this is usually called from the remove function, or from probe when something failed and hid_hw_start was already called. so you’re in cleanup mode, periodt 💅

and bestie, if the caller enabled HID input via hid_device_io_start and is unwinding without an explicit hid_device_io_stop, quiesce input first so that in-flight reports cannot reach handlers (e.g. hidraw_report_event) whose backing objects hid_disconnect is about to free. that caveat is important, fr fr — don’t let reports hit objects that are about to get freed 😭🔥

🌈 SEE ALSO 🌈

the kernel file is ./drivers/hid/hid-core.c, and the rest of the friend group is:

• hid_parse_report(9)
• hid_validate_values(9)
• hid_open_report(9)
• hid_match_report(9)
• hid_match_usage(9)
• hid_input_report(9)
• hid_safe_input_report(9)
• hid_hw_start(9)
• hid_hw_open(9)
• hid_hw_close(9)
• hid_hw_request(9)
• hid_hw_raw_request(9)
• hid_hw_output_report(9)
• new_id_store(9)
• hid_compare_device_paths(9)
• hid_allocate_device(9)
• hid_destroy_device(9)

with love from ./drivers/hid, October 2026, and hid_hw_stop(9) 🫶💖✨