__phy_read_mmd(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 __phy_read_mmd(9) 🌸

okay bestie, welcome to the Kernel API Manual — yes that Kernel API Manual, the one with the driest prose on planet earth, and we're about to make it cute 💅 this one's about reading a register off an MMD sitting on a PHY. tiny function, big main character energy, let's go 🫶

✨ NAME ✨

__phy_read_mmd — a convenience function for reading a register from an MMD on a given PHY ✨ like it literally says on the tin, no cap

🦋 SYNOPSIS 🦋

int __phy_read_mmd (struct phy_device *phydev , int devad , u32 regnum );

🎀 ARGUMENTS 🎀

  • phydev — the phy_device struct, aka the PHY you're poking at 💖
  • devad — the MMD you're reading from, valid range is 0..31 👑
  • regnum — the register on that MMD you wanna read, valid range is 0..65535 ⭐
not me stressing the ranges — devad is 0..31 and regnum is 0..65535, that's the whole vibe check, don't come for me 😭

💀 DESCRIPTION 💀

Same rules as for __phy_read — yep, that's it, that's the description, the kernel devs really said "iykyk" and dipped 🙈

So like, if you already know how __phy_read behaves, you already know what's up here. if you don't… maybe go read that one first bestie, I'm just the messenger 🧚

🌈 SEE ALSO 🌈

so many siblings, this function has a whole extended family fr fr — all chilling in the kernel file ./drivers/net/phy/phy-core.c:

aaaand that's the whole page, you ate that 💅 quick little sign-off so we're being responsible: this icon lives in ./drivers/net/phy, dated October 2026, and it's filed under __phy_read_mmd(9) 🍓 bye bestie, go read some registers 🦋

📦 where this page comes from