lwmi_cd_sub_component_bind(9)

📦 version 7.3.1, in nixpkgs unstable

💻 lwmi_cd_sub_component_bind(9) — Kernel API Manual ✨

okay bestie, welcome to the lwmi_cd_sub_component_bind page 🫶 this one lives in the Kernel API Manual and it's literally the moment a sub-component gets tied to its sub-master device. short page, big main character energy 👑

🌸 NAME 🌸

lwmi_cd_sub_component_bind — bind a sub-component to the sub-master device 💅

✨ SYNOPSIS ✨

int lwmi_cd_sub_component_bind (struct device *sc_dev , struct device
*sm_dev , void *data );

🎀 ARGUMENTS 🎀

  • sc_dev — pointer to the sub-component capdata parent device. yes, the sub-component one, don't mix her up with the other one 🙈
  • sm_dev — pointer to the sub-master capdata parent device. that's the sub-master, okay, two different devices, keep them straight bestie 💖
  • data — pointer that's used to return the capability data list pointer. she's an out-param, she carries the list pointer back out 🦋

🌈 DESCRIPTION 🌈

so here's the vibe: on the sub-master's bind, this function provides a pointer to the local capdata list 🎯 and that pointer is what the sub-master uses to call the master callback. that's it, that's the whole plot. not me being obsessed with how clean that is 😭✨

⭐ RETURN ⭐

returns 0 🎉 yeah. that's the whole return section. iconic, honestly.

🦋 SEE ALSO 🦋

the kernel file that has all the lore:

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

and the whole friend group 💜:

and that's the whole page, bestie 🌈💖 this little gem comes from ./drivers/platform/x86/lenovo, dated October 2026, and it's filed under lwmi_cd_sub_component_bind(9) — go read the rest of the family, ily, bye 🎀✨

📦 where this page comes from