mxl86110_mod...extended_reg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 mxl86110_mod...extended_reg(9) β€” the Kernel API Manual, bestie edition 🌸

okay so picture this: you're deep in the Kernel API Manual for mxl86110_mod...extended_reg(9) and you just need to flip some bits in a PHY's extended register without wrecking the rest of them. That's the whole vibe of this page. Let's go ✨


πŸ’– NAME πŸ’–

mxl86110_modify_extended_reg β€” modify bits of a PHY's extended register. that's it, that's the function, and honestly? she's iconic for it πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

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

πŸŽ€ ARGUMENTS πŸŽ€

  • phydev β€” pointer to the PHY device structure. your main character struct fr fr 🫢
  • regnum β€” register number to write. which register we're messing with πŸ’…
  • mask β€” bit mask of bits to clear. the "not these ones" list πŸ™ˆ
  • set β€” bit mask of bits to set. the "yes these ones actually" list ✨

⭐ NOTE ⭐

lowkey the most important line on this whole page, no cap:

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

that's the math, bestie. clear the mask bits, then OR in the set bits. it's giving surgical precision 🧚


🌈 RETURN 🌈

0 or negative error code. so like... zero means slay, negative means something went wrong and you should probably look at it 😭


πŸ”₯ SEE ALSO πŸ”₯

the whole friend group, gathered for you:


and that's the page!! go forth and modify those extended register bits responsibly, bestie πŸ’œ

mwah πŸ’‹ β€” this little number lives in ./drivers/net/phy, dated October 2026, and the header's still calling it mxl86110_mod...extended_reg(9) because we abbreviate when the name is too long to fit. periods, slay, bye πŸ‘‘

πŸ“¦ where this page comes from