hid_input_report(9)

okay bestie, welcome to the hid_input_report(9) page from the Kernel API Manual 💅✨ this is the group chat for report data, and yes, we’re keeping every detail.

💖 NAME 💖

hid_input_report — report data from lower layer (usb, bt...). That’s the whole name vibe: it’s the report-data messenger from the lower layers, no cap.

✨ SYNOPSIS ✨

here’s the signature, screenshot it:

int hid_input_report (struct hid_device *hid , enum hid_report_type type
, u8 *data , u32 size , int interrupt );

🎀 ARGUMENTS 🎀

• hid — the hid device. literally the HID device, the main character.
• type — HID report type (HID_*_REPORT), iykyk.
• data — report contents, the actual data payload.
• size — size of data parameter. yes, that data.
• interrupt — distinguish between interrupt and control transfers; it tells you which transfer vibe you’re in.

💅 DESCRIPTION 💅

This is data entry for lower layers. Legacy alert 🚨 — please use hid_safe_input_report instead. periodt, that’s the important part.

🦋 SEE ALSO 🦋

Kernel file: ./drivers/hid/hid-core.c — the source location, check it.

• hid_parse_report(9)
• hid_validate_values(9)
• hid_open_report(9)
• hid_match_report(9)
• hid_match_usage(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)

cute sign-off: source/version ./drivers/hid, dated October 2026, and the page is hid_input_report(9) — mwah 💋💖