__phy_write_mmd(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __phy_write_mmd(9) β€” from the Kernel API Manual, bestie

okay so listen up, because this one is lowkey a little shortcut function and it's giving "I do one thing and I do it well" energy ✨


🌸 NAME

__phy_write_mmd β€” the convenience function for writing a register on an MMD, on a given PHY. that's it, that's the whole vibe πŸŽ€


πŸ¦‹ SYNOPSIS

int __phy_write_mmd (struct phy_device *phydev , int devad , u32 regnum , u16 val );

she takes four things and hands you back an int, periodt πŸ’…


πŸ“ ARGUMENTS

  • phydev β€” the phy_device struct. your main character, the PHY herself 🫢
  • devad β€” the MMD to read from. yes, that's what the manpage says, we're just relaying it 🧚
  • regnum β€” the register on the MMD to read. again, verbatim, don't come for me 😭
  • val β€” the value to write to regnum. the actual payload, the reason we're all here πŸ”₯

πŸ‘‘ DESCRIPTION

Same rules as for __phy_write β€” that's it, that's the description. no cap. if you know __phy_write, you already know this one; they share the same rules, so go read that one for the deets, iykyk πŸ’–

ngl, the original page is short and she's staying short. the facts are the facts, bestie πŸ’€

🌈 SEE ALSO

Kernel file ./drivers/net/phy/phy-core.c and honestly a whole friend group of functions, all of them iconic, all of them linked here so you can go say hi πŸ‘‘


and that's the whole page, bestie πŸŽ€ huge shoutout to the ./drivers/net/phy directory for hosting all this excellence, and to the October 2026 edition of the Kernel API Manual for shipping it β€” slay, ate, no crumbs πŸ’œπŸ¦‹βœ¨

πŸ“¦ where this page comes from