__phy_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– __phy_write(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for __phy_write πŸ’… β€” yes, the double-underscore one. It's literally a convenience function for writing a given PHY register, and the vibe is very β€œsmall helper, big main character energy” ✨. No cap.

🌸 NAME 🌸

__phy_write β€” convenience function for writing a given PHY register πŸŽ€

✨ SYNOPSIS ✨

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

πŸŽ€ ARGUMENTS πŸŽ€

  • phydev β€” the phy_device struct 🫢
  • regnum β€” register number to write, iykyk πŸ”₯
  • val β€” value to write to regnum πŸ’œ

πŸ”₯ DESCRIPTION πŸ”₯

okay so, real talk: the caller must have taken the MDIO bus lock. No cap. That's the whole requirement, and it is not optional β€” the caller must have taken the MDIO bus lock. Periodt. πŸ’…

🚨 bestie, this is the important caveat: the caller must have taken the MDIO bus lock. Do not sleep on it.

🌈 SEE ALSO 🌈

okay bestie, this list is literally a whole group chat β€” every single reference is here, no cap πŸ‘‘:


mwah πŸ’‹ this page is from the ./include/linux source/version and is dated October 2026 β€” __phy_write(9) fr fr, periodt. 🫢

πŸ“¦ where this page comes from