hid_bpf_try_input_report(9)

💅 hid_bpf_try_input_report(9)

okay so bestie, welcome to the Kernel API Manual 🎀 — this one's called hid_bpf_try_input_report, and it's literally the "no cap, just send it" version of injecting a HID report straight from a HID device into the kernel ✨

---

⭐ NAME ⭐

hid_bpf_try_input_report — inject a HID report in the kernel from a HID device 🦋

---

✨ SYNOPSIS ✨

__bpf_kfunc int hid_bpf_try_input_report (struct hid_bpf_ctx *ctx , enum
hid_report_type type , u8 *buf , const size_t buf__sz );

like, copy that exactly, don't come for me 🙈

---

🫶 ARGUMENTS 🫶

• ctx — the HID-BPF context that you already made earlier in hid_bpf_allocate_context, bestie. no context, no vibes 💅
• type — the type of the report, and it's one of HID_INPUT_REPORT, HID_FEATURE_REPORT, or HID_OUTPUT_REPORT 👑
• buf — a PTR_TO_MEM buffer, iconic
• buf__sz — the size of the data to transfer, fr fr, count it correctly 🍓

---

🌸 DESCRIPTION 🌸

Returns 0 on success, and a negative error code otherwise 😭 — that's the whole mood.

The way this works: it will immediately fail if the device is not available, so it's totally safe to use in IRQ context 🔥. that's the main character energy right there — no blocking, no waiting, just a quick vibe check and out ✨💀

---

💜 SEE ALSO 💜

• Kernel file ./drivers/hid/bpf/hid_bpf_dispatch.c
• hid_bpf_get_data(9)
• hid_bpf_allocate_context(9)
• hid_bpf_release_context(9)
• hid_bpf_hw_request(9)
• hid_bpf_hw_output_report(9)
• hid_bpf_input_report(9)

go read those too, iykyk 📚🦋

---

ngl this page's home directory is ./drivers/hid/bpf and it's dated October 2026 — so yeah, mark your calendars and hydrate 💖

that's the whole page bestie, slay, periodt, go inject some reports responsibly 🌈👑🧚