hid_safe_input_report(9)

📦 version 7.3.1, in nixpkgs unstable

💖 hid_safe_input_report(9) 💖

okay so bestie, welcome to the hid_safe_input_report glow-up page — it's a kernel API manual moment and we're gonna make it make sense, no cap.

✨ NAME ✨

hid_safe_input_report — the one that reports data from the lower layer (usb, bt... you know the vibes) 🫶

🌸 SYNOPSIS 🌸

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

🎀 ARGUMENTS 🎀

  • hid — the hid device itself, the main character here 👑
  • type — which HID report type it is (HID_*_REPORT), like identifying the vibe check ✨
  • data — the actual report contents, the whole point of showing up 💅
  • bufsize — how much space was actually allocated for the data buffer, aka the ceiling on the whole situation
  • size — the useful size of the data parameter, aka how much of it is real
  • interrupt — tells you whether it's an interrupt transfer or a control transfer, so the function knows which lane it's in 🦋

⭐ DESCRIPTION ⭐

This is literally the data entry point for the lower layers. Please use this function instead of the non-safe version — and bestie, I'm not being dramatic: we hand over the size of the buffer here, which lets hid-core make smarter decisions about the incoming buffer. that's the whole flex 😭💖

🌈 SEE ALSO 🌈

Kernel file ./drivers/hid/hid-core.c — and the whole friend group:

that's the whole page, periodt ✨ this one lives over in ./drivers/hid and it's dated October 2026 — write that down, iykyk 🗓️💜

📦 where this page comes from