lwmi_cd_component_bind(9)

📦 version 7.3.1, in nixpkgs unstable

💅 lwmi_cd_component_bind — bestie's guide to the kernel API manual 💅

okay so this whole page is about one function, and it's lwmi_cd_component_bind, and it lives in the kernel API manual. yes, the kernel. we're doing this. 🎀

✨ NAME ✨

lwmi_cd_component_bind — literally just binds a component to the master device. that's the whole vibe. 🦋

🌸 SYNOPSIS 🌸

int lwmi_cd_component_bind (struct device *cd_dev , struct device
*om_dev , void *data );

three args, returns an int. no cap. 💅

🎀 ARGUMENTS 🎀

  • cd_dev — pointer to the lenovo-wmi-capdata driver parent device. that's the capdata one, bestie, keep them straight 🫶
  • om_dev — pointer to the lenovo-wmi-other driver parent device. yes there's an "other" one too 😭
  • data — an lwmi_cd_binder object pointer, and its whole job is to return the capability data back to you. it's giving delivery service ✨

💖 DESCRIPTION 💖

so when lenovo-wmi-other's master does its bind, this is what hands over a pointer to the local capdata list. iconic behavior honestly 👑

and what's that pointer for? it's used to call lwmi_cd*_get_data so you can look up attribute data from the lenovo-wmi-other driver. that's the whole plot. 🌈

also — if cd_dev happens to be a sub-master, it tries to call the master callback. note the "tries", it's not out here making promises 🙈

⭐ RETURN ⭐

0

that's it. that's the return value. zero. slay. 🎉

🦋 SEE ALSO 🦋

first up, the kernel file itself:

  • Kernel file ./drivers/platform/x86/lenovo/wmi-capdata.c

and then, like, the entire extended friend group 💀 (they all showed up to the function, no one was left out):

periodt. 💜

ngl, that see-also list is a whole friend group chat and you're now in it. 🍓

and that's the page!! 🧚 this little beauty came from ./drivers/platform/x86/lenovo and it's dated October 2026, so yeah, future vibes only ⭐ mwah, go read the source 💋

📦 where this page comes from