hid_ishtp_get_report(9)

📦 version 7.3.1, in nixpkgs unstable

💅 hid_ishtp_get_report — the Kernel API Manual, bestie edition ✨

okay so real talk, this page lives in the Kernel API Manual (section 9, hid_ishtp_get_report(9), yes that's the whole name, it's giving main character energy) and it's about asking for a feature/input report. let's get into it 🫶

🌸 NAME 🌸

hid_ishtp_get_report — the "hey bestie can u send me a report" request, for feature/input reports 💖

✨ SYNOPSIS ✨

void hid_ishtp_get_report (struct hid_device *hid , int report_id , int
report_type );

no cap, that's the whole signature. she takes three things and returns void (nothing back, we'll get to why that's lowkey the whole point) 🎀

🦋 ARGUMENTS 🦋

  • hid — the hid device instance that this request is for. like, which device are we talking to, bestie 👑
  • report_id — the report id for the get request. yes you have to know which one, no she will not guess for you 🙈
  • report_type — the report type for this request. tell her what kind of report you're after 🍓

💜 DESCRIPTION 💜

so this function gets called from the hid core .request callback. literally that's her whole gig ✨

what she does: sends the request off to the FW (firmware, iykyk) and then returns without waiting for a response. periodt. she's not sticking around, she's not refreshing her messages, she just fires it off and dips 💅

🫶 important vibe check: this is fire-and-forget. if you're expecting her to hang around and hand you the answer, she is Not Doing That. no cap.

🌈 SEE ALSO 🌈

the group chat, aka everyone else in the same kernel file, ./drivers/hid/intel-ish-hid/ishtp-hid-client.c:

go say hi, they're all icons 🔥

okay that's the page, mwah 💋 — sourced from ./drivers/hid/intel-ish-hid, dated October 2026, and the whole thing is filed under hid_ishtp_get_report(9) in case you forgot already (you didn't, you're doing amazing) 🌟

📦 where this page comes from