bus_register(9)

📦 version 7.3.1, in nixpkgs unstable

💖 bus_register(9) 💖

okay bestie, welcome to the kernel API manual, and today's main character is bus_register(9) — like, this is the kernel-doc page from the good people over in the kernel API manual department, and it's honestly giving "small function, huge responsibility." 🦋

✨ NAME ✨

bus_register — register a driver-core subsystem. that's it, that's the whole vibe check. 👑

✨ SYNOPSIS ✨

int bus_register (const struct bus_type *bus );

lowkey the cleanest little signature ever, ngl. 🎀

✨ ARGUMENTS ✨

  • bus — the bus to register 💅 this is the one (1) thing you're handing over, so make it count.

✨ DESCRIPTION ✨

okay so picture this 🫶 once we have that, we register the bus with the kobject infrastructure, and then we register the children subsystems it has: the devices and drivers that belong to the subsystem. like, the whole fam gets introduced, not just the bus itself. so iconic of it. ✨

and yes, both of those are the children subsystems of your bus — the devices, and the drivers — and they're literally the whole point. the way the kernel just builds a little family tree and tells kobjects about every single member... obsessed. 🌸

✨ SEE ALSO ✨

the kernel file ./drivers/base/bus.c is where all the lore lives, and here's the full squad of cross-references — no cap, all of them, not a single one skipped: 💜

like a whole friend group of functions and every one of them is invited to the group chat. 🔥

psa bestie: this page lives in ./drivers/base and it's dated October 2026 — so when you cite it, cite it with your whole chest. 🧚

okay that's the page!! stay slay, register those buses, and remember: kobject infrastructure first, children subsystems second. periodt. 💅💖🌈

📦 where this page comes from