ytphy_utp_read_abilities(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ytphy_utp_read_abilities(9) β€” the Kernel API Manual glow-up ✨

okay so bestie, welcome to the Kernel API Manual page for ytphy_utp_read_abilities(9) β€” she's a little function with main character energy and honestly? she ate. let's get into it πŸŽ€


✨ NAME ✨

ytphy_utp_read_abilities β€” reads the PHY's abilities straight out of the Clause 22 registers πŸ¦‹


🌸 SYNOPSIS 🌸

int ytphy_utp_read_abilities (struct phy_device *phydev );

like yes she takes exactly one (1) argument and returns an int, no notes πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • phydev β€” your target phy_device struct, aka the little guy you're about to interrogate 🫢

πŸ’œ NOTE πŸ’œ

okay so here's the tea: this function reads the PHY's abilities and populates phydev->supported accordingly. like it's literally filling in the vibe check of what this PHY can do πŸ’«

⚠️ but bestie, the caller must have taken the MDIO bus lock already. no cap, that's non-negotiable. don't be out here touching registers unlocked, that's not the move 😭

and she returns 0 or a negative errno code. that's it. that's the whole mood πŸ“


🌈 SEE ALSO 🌈

the whole friend group, in the kernel file ./drivers/net/phy/motorcomm.c β€” iykyk πŸ‘‘


and that's the page, diva πŸ’… this whole thing lives in ./drivers/net/phy, stamped October 2026 β€” go forth and lock that MDIO bus before you call her, mwah πŸ˜˜πŸ¦‹

πŸ“¦ where this page comes from