mdio_find_bus(9)

💖 mdio_find_bus(9) 💖

okay so bestie, welcome to the mdio_find_bus page — this is a kernel API manual entry, and we're gonna get you comfy with it in like two minutes flat. no cap.

---

🎀 NAME 🎀

mdio_find_bus — give it the name of a mdiobus and it finds you the mii_bus. that's the whole vibe. it's giving "search bar for buses" ✨

---

🌸 SYNOPSIS 🌸

struct mii_bus * mdio_find_bus (const char *mdio_name );

like, that's it. one call, one arg, one pointer back. iconic behavior honestly 💅

---

🦋 ARGUMENTS 🦋

• mdio_name — the name of a mdiobus. yes, that's the actual name. it's literally a string with the bus name in it. you pass it in, the function goes looking. 🕵️‍♀️

---

👑 RETURN 👑

so here's what you get back:

• a reference to the mii_bus — slay, you found it 🎉
• NULL — if none found. sad girl hours, the bus doesn't exist 😭

⚠️ important, don't skip this part bestie: when you DO get a bus back, the embedded struct device will have its reference count incremented. that means you gotta put_deviced it once the bus is finished with. fr fr, do not forget — this is the kind of thing that comes back to haunt you 🫶

---

🌈 SEE ALSO 🌈

the whole friend group, in kernel file ./drivers/net/phy/mdio_bus_provider.c:

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

iykyk — go read them all, they're all bangers 💜

---

mwah, that's the page! 🍓 this one lives in the kernel source tree at ./drivers/net/phy, and it's dated October 2026. take care of your refcounts and you'll be fine. byeeeee 💖✨