__mxl86110_m...extended_reg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the __mxl86110_m...extended_reg(9) page from the Kernel API Manual β€” yes, the title is a whole mouthful 😭 but we’re here and we’re slaying πŸ’…

🌸 NAME 🌸

__mxl86110_modify_extended_reg β€” modify bits of a PHY’s extended register

✨ SYNOPSIS ✨

int __mxl86110_modify_extended_reg (struct phy_device *phydev , u16
regnum , u16 mask , u16 set );

πŸŽ€ ARGUMENTS πŸŽ€

  • phydev β€” pointer to the PHY device structure. It’s the PHY bestie we’re working with 🫢
  • regnum β€” register number to write. The exact extended register you’re aiming at.
  • mask β€” bit mask of bits to clear. These are the bits getting turned off.
  • set β€” bit mask of bits to set. These are the bits getting turned on.

πŸ‘‘ NOTE πŸ‘‘

the formula is literally:

register value = (old register value & ~mask) | set.

Also, big caveat, no cap: this function assumes the caller already holds the MDIO bus lock or otherwise has exclusive access to the PHY. So yeah, that access situation has to be handled before you go modifying bits πŸ’€

πŸ”₯ RETURN πŸ”₯

0 or negative error code. That’s the whole vibe check β€” zero or a negative error code.

πŸ¦‹ SEE ALSO πŸ¦‹


and that’s the page, bestie 🫢 β€” source/version and date vibes: ./drivers/net/phy Β· October 2026 Β· filed under __mxl86110_m...extended_reg(9). periodt πŸ’–

πŸ“¦ where this page comes from