component_master_del(9)

💅 component_master_del(9)

okay so this is from the Kernel API Manual bestie, and it's literally the cleanup queen of the component subsystem — the one you call when the aggregate driver era is over 👑

---

✨ NAME ✨

component_master_del — unregister an aggregate driver 🫶

---

🌸 SYNOPSIS 🌸

void component_master_del (struct device *parent , const struct
       component_master_ops *ops );

---

🎀 ARGUMENTS 🎀

• parent — parent device of the aggregate driver 💖
• ops — callbacks for the aggregate driver ✨

---

🦋 DESCRIPTION 🦋

So here's the tea: this function unregisters an aggregate driver that was registered with component_master_add_with_match. Simple, clean, no cap.

And if necessary — like, if it has to happen — the aggregate driver is first disassembled by calling component_master_ops.unbind from ops. So it's not just "bye", it's "bye, but let me take the whole thing apart properly first" 💅 iconic behaviour honestly.

lowkey important: the teardown ordering is the whole point here. It unbinds first if needed, then unregisters. The manpage says "if necessary", so don't come for me about when it's necessary — that's the kernel's call, not mine 🙈

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/base/component.c
• overview(9)
• component_compare_of(9)
• component_release_of(9)
• component_compare_dev(9)
• component_compare_dev_name(9)
• component_match_add_release(9)
• component_match_add_typed(9)
• component_master_add_with_match(9)
• component_unbind_all(9)
• component_bind_all(9)
• component_add_typed(9)
• component_add(9)
• component_del(9)

like. read the whole component.c family, it's giving "found family" fr fr 💜

---

🫶 okay bye bestie, this page lives in ./drivers/base, the version vibe is October 2026, and the whole thing answers to the name component_master_del(9) — slay, go unregister something responsibly 💖✨