lwmi_cd_component_unbind(9)

📦 version 7.3.1, in nixpkgs unstable

💅 lwmi_cd_component_unbind(9) — the unbind one, bestie

okay so hi 🫶 you've landed on a page from the Kernel API Manual, and it's literally about lwmi_cd_component_unbind. Yes the name is a mouthful, no we're not renaming it, it's iconic as-is. Let's get into it ✨

🌸 NAME 🌸

lwmi_cd_component_unbind — unbind component to master device. That's the whole errand. 💅

🦋 SYNOPSIS 🦋

void lwmi_cd_component_unbind (struct device *cd_dev , struct device *om_dev , void *data );

🎀 ARGUMENTS 🎀

  • cd_dev — a pointer to the lenovo-wmi-capdata driver parent device. main character energy fr 🌟
  • om_dev — a pointer to the lenovo-wmi-other driver parent device. also showing up, also valid 💜
  • data — unused. literally just vibing there 😭 not doing a single thing

🔥 DESCRIPTION 🔥

so here's the tea ☕ — if cd_dev is a sub-master, the function clears the collected data from the master device.

why tho? because we're preventing a whole mess: it stops the binding establishment between the sub-master and the sub-component from calling the master callback. like, if that binding is about to happen, we're shutting it down before it can slide into the master callback uninvited 🙈. protective queen behavior, ngl.

👑 SEE ALSO 👑

like, that's the whole friend group, go say hi to all of them 🫶

lowkey a reminder: data genuinely does nothing here. don't go looking for hidden lore, there is none 💀

and that's the page!! mwah 💋 it lives under ./drivers/platform/x86/lenovo, stamped with the date October 2026 — go read the rest of the girls, they ate too. periodt 🎀✨🌸

📦 where this page comes from