__mdiobus_register(9)

💖 __mdiobus_register(9) 💖

okay so this is the __mdiobus_register(9) page from the Kernel API Manual, and honestly? it's giving “bus driver glow-up” energy. let's get into it bestie 🫶

---

🌸 NAME 🌸

__mdiobus_register — bring up all the PHYs on a given bus and attach them to bus

---

✨ SYNOPSIS ✨

int __mdiobus_register (struct mii_bus *bus , struct module *owner );

---

🎀 ARGUMENTS 🎀

• bus — the target mii_bus 👑
• owner — the module containing bus accessor functions 🧚

---

🦋 DESCRIPTION 🦋

So this function gets called by a bus driver to bring up all the PHYs on a given bus, and attach them to the bus. main character behavior, honestly 💅

🚨 lowkey important: drivers should use mdiobus_register rather than __mdiobus_register unless they need to pass a specific owner module. like, don't reach for the double-underscore one for no reason, bestie 😭

MDIO devices which are not PHYs will not be brought up by this function. they are expected to be explicitly listed in DT and instantiated by of_mdiobus_register. periodt ✨

Returns 0 on success or < 0 on error. that's it, that's the vibe check 🌈

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/net/phy/mdio_bus_provider.c and these besties:

• mdiobus_release(9)
• mdio_bus_match(9)
• mdiobus_alloc_size(9)
• mdiobus_scan_c22(9)
• mdiobus_scan_c45(9)
• mdiobus_free(9)
• mdio_find_bus(9)
• of_mdio_find_bus(9)

---

and that's the page, bestie 💖 signing off with the footer deets: source/version ./drivers/net/phy, dated October 2026. mwah 💋🎀