ytphy_read_ext(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ytphy_read_ext(9) πŸ’–

okay bestie, we're in the ytphy_read_ext(9) page in the Kernel API Manual, and this one is short, sweet, and lowkey iconic. It reads a PHY's extended register. That's the whole assignment, and it ate.

🌸 NAME 🌸

ytphy_read_ext β€” read a PHY's extended register. Exactly what it says on the tin, and the tin is cute.

✨ SYNOPSIS ✨

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

🫢 ARGUMENTS 🫢

  • phydev β€” a pointer to a struct phy_device. It's the PHY device you're working with, bestie.
  • regnum β€” register number to read. This is the extended-register address you want the tea from.

⚠️ NOTE ⚠️

Lock moment, fr fr: the caller must have taken the MDIO bus lock.

After that, it returns the value of regnum reg or negative error code. That's it β€” no extra lore, no cap.

πŸ‘€ SEE ALSO πŸ‘€

The kernel file is ./drivers/net/phy/motorcomm.c, and here's the whole iconic friend group:


sign-off time, bestie: from ./drivers/net/phy, October 2026 β€” this was ytphy_read_ext(9) πŸ’…βœ¨

πŸ“¦ where this page comes from