ytphy_write_ext_with_lock(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ytphy_write_ext_with_lock(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual β€” yes we're reading kernel docs for fun now, that's the vibe πŸ’…


✨ NAME ✨

ytphy_write_ext_with_lock β€” writes to a PHY's extended register 🫢 lowkey does exactly what it says on the tin


🌸 SYNOPSIS 🌸

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

πŸŽ€ ARGUMENTS πŸŽ€

  • phydev β€” a pointer to a struct phy_device πŸ¦‹ (yes it's a pointer, yes you have to pass it, no we can't skip it)
  • regnum β€” the register number you wanna write to ⭐
  • val β€” the value that's gonna go into regnum ✨

πŸ‘‘ DESCRIPTION πŸ‘‘

returns 0 or negative error code 😭 that's literally it, that's the whole description. zero means slay, negative means something went sideways ngl.


🧚 SEE ALSO 🧚

first up, the file itself: Kernel file ./drivers/net/phy/motorcomm.c β€” that's where all this lives, iykyk πŸ’œ

and now the whole friend group, in order, no skips fr fr:

like, that's forty-eight whole entries bestie, we did not skip a single one, main character energy only πŸ‘‘


no cap: this page lives in ./drivers/net/phy, dated October 2026 🌈

that's the whole manual, bestie β€” go write some extended registers responsibly πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from