ishtp_hbm_c..._control_req(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME

ishtp_hbm_cl_flow_control_req — bestie, this one sends a flow control request. That's the whole vibe. 🦋

(also hi, welcome to the Kernel API Manual, section 9 — the header up top truncates the name all cute like ishtp_hbm_c..._control_req(9) but we know the full one now 💖)

✨ SYNOPSIS ✨

int ishtp_hbm_cl_flow_control_req (struct ishtp_device *dev , struct
       ishtp_cl *cl );

okay so it returns an int, and it takes two things: a device and a client. iconic signature, no notes 🔥

🎀 ARGUMENTS 🎀

  • dev — the ISHTP device instance. your actual hardware situation, the main character of this call 🌸
  • cl — the ISHTP client instance. the client that's getting the flow control request, she's the one being addressed 💅

🧚 DESCRIPTION 🧚

Send flow control request. that's it, that's the description, and honestly? sometimes the function name is the documentation. it's giving "self-explanatory" and we respect it 👑

so: you've got a client (cl), you've got a device (dev), and this here function is the one that ships off the flow control request for that client. literally just send flow control request. periodt. 😭

⭐ RETURN ⭐

  • 0 if success — slay, we love a zero 💖
  • else error code — ngl if you get anything that isn't 0, that's not success, and it's an error code, so like… handle it 🫶

🌈 SEE ALSO 🌈

the whole friend group, fr fr — every one of these is in Kernel file ./drivers/hid/intel-ish-hid/ishtp/hbm.c:

ok that's the whole page, no gatekeeping 💀 everything above is exactly what the man page says, just with better energy ✨

anyway bestie, that's a wrap — this page lives in ./drivers/hid/intel-ish-hid/ishtp, it's from the Kernel API Manual gang, dated October 2026, and the header's official truncated name is ishtp_hbm_c..._control_req(9). go forth and flow control 🎀💜

📦 where this page comes from