ytphy_read_ext_with_lock(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ytphy_read_ext_with_lock(9) 🦋

okay bestie, welcome to the Kernel API Manual ✨ this one's a lil function from the kernel side of things and she's honestly so simple it's giving main character energy for a one-liner. let's get into it 🫶

✨ NAME ✨

ytphy_read_ext_with_lock — reads a PHY's extended register 💖

like, that's her whole job. one (1) job. and she ate.

🌸 SYNOPSIS 🌸

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

yes the spacing before the commas is exactly like that, don't @ me, that's just how she was written 💀

🎀 ARGUMENTS 🎀

  • phydev — a pointer to a struct phy_device 🧚 that's your PHY, your whole vibe, the device you're doing the thing to
  • regnum — register number to read 🌸 the u16 one. that's the extended register you're peeking at

💜 DESCRIPTION 💜

so basically 👑 it returns the value of regnum reg — that's your read, bestie, the actual contents of the extended register — or negative error code 😭 which is the "nope, didn't work" branch. so like... check the return value, fr fr, don't just assume it's data 🙈

lowkey the most important thing here: it can hand you back an error instead of a register value, so vibe-check that int before you go treating it like real data 💀

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/net/phy/motorcomm.c and honestly? she has SO many siblings. like a whole extended family reunion. here's every single one, no cap, none skipped 👑

like I said. huge family. iykyk 🦋

and that's the page, bestie ✨ this one came out of ./drivers/net/phy, dated October 2026, and she's ytphy_read_ext_with_lock(9) through and through 💅 go read some extended registers responsibly, ily 🫶🎀

📦 where this page comes from