mxl86110_read_extended_reg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mxl86110_read_extended_reg(9) β€” the Kernel API Manual, but make it make sense

okay so bestie, welcome to the Kernel API Manual, section 9 (that's the kernel-functions girlies 🌸). Today's main character is mxl86110_read_extended_reg, and no cap, she is literally just here to read a register for you. Let's get into it 🫢


✨ NAME ✨

mxl86110_read_extended_reg β€” read a PHY's extended register. that's it. that's the whole job. iconic behaviour, honestly πŸ‘‘


πŸŽ€ SYNOPSIS πŸŽ€

int mxl86110_read_extended_reg (struct phy_device *phydev , u16 regnum );

copy it exactly, don't @ me πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • phydev β€” pointer to the PHY device structure. yes queen, she needs to know which PHY we're talking to 🧚
  • regnum β€” the extended register number to read. tell her which one and she'll go get it ✨

🌈 DESCRIPTION 🌈

so what does she actually do? she reads from an extended register of the PHY using the MaxLinear two-step access method (that's reg 0x1E/0x1F, iykyk). her party trick: she handles acquiring and releasing the MDIO bus lock internally, all by herself, so you don't have to think about it 🫢 lock in, lock out, no drama, periodt.


πŸ”₯ RETURN πŸ”₯

on success you get the 16-bit register value back πŸ’–. on failure you get a negative errno code β€” so like, check for that, bestie, don't just vibe with a negative number 😭


⭐ SEE ALSO ⭐

the whole extended-register friend group ate, ngl πŸ”₯


lowkey a whole squad of mxl86110_* and mxl86111_* functions, and every single one is worth a read. main character energy across the board πŸ‘‘

okay that's the page!! πŸŽ€ this lil' baddie lives over in ./drivers/net/phy, she's dated October 2026, and she's filed under mxl86110_read_extended_reg(9) in the Kernel API Manual. go forth and read those extended registers, bestie β€” slay πŸ’œπŸ¦‹βœ¨

πŸ“¦ where this page comes from