lwmi_cd_sub_master_unbind(9)

📦 version 7.3.1, in nixpkgs unstable

💅 lwmi_cd_sub_master_unbind(9) — Kernel API Manual ✨

okay so bestie, welcome to lwmi_cd_sub_master_unbind from the Kernel API Manual — this is the one that breaks up the situationship between a sub-master device and its sub-component. it's giving "we need to talk" but in C. 🫶

🌸 NAME 🌸

lwmi_cd_sub_master_unbind — unbind the sub-component of a sub-master device. literally that's the whole job. 💅

🦋 SYNOPSIS 🦋

void lwmi_cd_sub_master_unbind (struct device *dev );

no return value, no drama, just vibes and a void. ✨

🎀 ARGUMENTS 🎀

  • dev — the sub-master capdata basic device. yes, that one. the sub-master. the basic device. the capdata one. 😌

🔥 DESCRIPTION 🔥

okay so here's the tea, and it's actually important so listen up 👑

First thing it does: it clears the collected pointer to the sub-component list. why?? because if a binding between the sub-master and the sub-component is about to happen, that stale pointer would let it call the master callback — and we are NOT doing that. nope. not today. clearing the pointer prevents that whole mess from going down. 🙈

Then, once that's handled, it calls component_unbind_all to unbind the sub-component device from the sub-master device. and that's it. that's the function. clean, simple, iconic. 🧚

🌈 SEE ALSO 🌈

the kernel file lives right here, bestie:

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

and here's the full squad — every single one of them, no cap:

and that's the whole page, bestie!! 💖 this came from ./drivers/platform/x86/lenovo and it's dated October 2026, so jot that down in your notes app 📝✨ mwah, go unbind something responsibly 🎀🦋💜

📦 where this page comes from