mdio_bus_match(9)

📦 version 7.3.1, in nixpkgs unstable

💖 mdio_bus_match(9) — the kernel API manual, bestie edition 💖

okay so this is a page from the Kernel API Manual (that's the manual name, iykyk) and it's about mdio_bus_match — one tiny function doing one very important vibe check. let's get into it 🫶

✨ NAME ✨

mdio_bus_match — determine if given MDIO driver supports the given MDIO device

like, literally just: does this driver fw this device? yes or no. main character energy for a bool 💅

✨ SYNOPSIS ✨

int mdio_bus_match (struct device *dev , const struct device_driver *drv );

that's it. that's the whole signature. no cap. 🎀

✨ ARGUMENTS ✨

  • dev — target MDIO device 🌸 (the device being checked, the one we're asking about)
  • drv — given MDIO driver ⭐ (the driver we're asking about, as in: do you support this device or not)

✨ RETURN ✨

  • 1 if the driver supports the device 🔥
  • 0 otherwise 💀

binary. iconic. periodt.

✨ DESCRIPTION ✨

so here's the tea 🍓: this may require calling the device's own match function, because different classes of MDIO devices have different match criteria.

read that again bestie — different classes of MDIO devices have different match criteria. so there's no universal one-size-fits-all check here, and the function might have to delegate to the device's own match function to figure it out. it's giving "let them introduce themselves" energy 🙈

✨ SEE ALSO ✨

the whole friend group 🧚 — Kernel file ./drivers/net/phy/mdio_bus_provider.c and honestly the entire squad:

go read those next, bestie, they're all linked up and lowkey obsessed with each other 🌈

ngl this one's a short page — but every single word of it is load-bearing, so don't skip the DESCRIPTION just because it's one sentence 💜

and that's a wrap, babe! 🎀 this page lives at ./drivers/net/phy and it's dated October 2026 — so yeah, future-timestamped, slay, we love a time traveler 👑✨ see you in the next manpage! 💖🦋

📦 where this page comes from