hid_match_report(9)

💅 hid_match_report: the vibe check for your HID driver ✨

Okay so bestie, first things first — this whole page is about hid_match_report, bestie. That's the function. Say hi. 👋

---

🌸 NAME 🌸

hid_match_report — check if driver's raw_event should be called

---

🎀 SYNOPSIS 🎀

int hid_match_report(struct hid_device *hid, struct hid_report *report);

---

🦋 ARGUMENTS 🦋

• hid — the hid device, the main character of this whole situation 👑
• report — the hid report we're matching against, aka the thing getting checked, no cap

---

💖 DESCRIPTION 💖

Lowkey the whole job is this: compare hid->driver->report_table->report_type to report->type. That's it. That's the function. You're comparing a type to a type — literally doing a vibe check between the driver's report table and the actual report. Periodt. 💅

---

⭐ SEE ALSO ⭐

The kernel file ./drivers/hid/hid-core.c and the whole friend group of HID functions, all linked up:

• hid_parse_report(9)
• hid_validate_values(9)
• hid_open_report(9)
• hid_match_usage(9)
• hid_input_report(9)
• hid_safe_input_report(9)
• hid_hw_start(9)
• hid_hw_stop(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)

---

Okay that's the whole page, bestie — sending hugs and good vibes 🫶, and this masterpiece lives at ./drivers/hid, dated October 2026. Slay. 💜💫