mxl86110_write_extended_reg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mxl86110_write_extended_reg(9) πŸ’…

okay so you're in the Kernel API Manual bestie, and this page is literally all about one little function. grab a strawberry πŸ“ and let's go.


✨ NAME ✨

mxl86110_write_extended_reg β€” writes to a PHY's extended register. that's it, that's the vibe. πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

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

like… three args, one int coming back. main character signature honestly. ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • phydev β€” pointer to the PHY device structure. yes bestie, the whole device. iconic.
  • regnum β€” the register number you wanna write to. pick your fave 🎯
  • val β€” the value going into regnum. this is the payload, the moment, the reason we're all here πŸ’…

🌸 DESCRIPTION 🌸

so this function writes to an extended register on the PHY, and the way it does that is the MaxLinear two-step access method using registers 0x1E/0x1F. two steps, no cap. 🫢

and the part i'm obsessed with? it handles acquiring and releasing the MDIO bus lock internally. you don't gotta do anything, it's already done. lock, do the thing, unlock. responsible queen behavior πŸ‘‘βœ¨


⭐ RETURN ⭐

0 or a negative error code. that's the whole story. zero means slay, negative means 😭


πŸ’œ SEE ALSO πŸ’œ

literally the whole friend group, go read them all, iykyk 🌈


ok final sign-off because we're fancy: this little baddie lives in ./drivers/net/phy, dated October 2026, and the page is mxl86110_write_extended_reg(9). periodt. πŸ’…πŸŽ€βœ¨
πŸ“¦ where this page comes from