ishtp_cl_bus_match(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ishtp_cl_bus_match(9) — the kernel API manual, but make it make sense

okay so bestie, welcome to ishtp_cl_bus_match(9) ✨ this is a page from the kernel API manual, and honestly? it's short, it's sweet, and it's about to be your new fave little matchmaker function 🎀

🌸 NAME 🌸

ishtp_cl_bus_match — literally the bus match() callback 🦋 no cap, that's the whole name.

✨ SYNOPSIS ✨

int ishtp_cl_bus_match (struct device *dev , const struct device_driver
       *drv );

that's it. that's the signature. she's serving function prototype realness 💅

🫶 ARGUMENTS 🫶

  • dev — the device structure. the actual device girlie in question 👑
  • drv — the driver structure. the driver she might be matching with 🎀

🔥 DESCRIPTION 🔥

okay so listen up, because this is the important part 🔥

This is a bus match callback — like, the wingman of the ishtp world 💖 It gets called when a new ishtp_cl_device is registered during ishtp bus client enumeration. and what does it do? it looks at the guid_t in drv and in dev, and uses those to decide whether they match or not 🦋 iykyk, it's giving compatibility check, it's giving "are you two meant to be" energy.

no extra vibes, no guessing — just guid-based matchmaking, periodt ✨

⭐ RETURN ⭐

  • 1 if dev & drv match 💖 (slay, they're a match)
  • 0 otherwise 🙈 (it's not giving, moving on)

🌈 SEE ALSO 🌈

the whole friend group, fr fr 🫶 get to know the fam:

lowkey reminder bestie: this page lives in ./drivers/hid/intel-ish-hid/ishtp 💜 and the date on it is October 2026 🌸 so go check the source files if you want the deep lore, okurrr 🧚

and that's the whole page, mwah 💋 go match some devices, you got this 🫶✨🎀

📦 where this page comes from