genphy_c37_read_status(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

okay so bestie, welcome to the manual page for genphy_c37_read_status (9) β€” yes the (9) means it lives in the kernel API section of the manual, we love a section number moment. This one is genuinely so cute and small: it checks the link and updates the current link state. That's it. That's the whole vibe. Let's go πŸ¦‹


✨ NAME ✨

genphy_c37_read_status β€” check the link status and update current link state πŸŽ€


🌸 SYNOPSIS 🌸

int genphy_c37_read_status (struct phy_device *phydev , bool *changed );

like, two args, one int back. she's lowkey minimal and I respect it πŸ’…


🫢 ARGUMENTS 🫢

  • phydev β€” the target phy_device struct, i.e. the PHY we're looking at. main character energy, honestly πŸ‘‘
  • changed β€” a pointer to where we store whether the link changed. she's an out-param, so we're writing through her, not copying her πŸ’–

πŸ”₯ DESCRIPTION πŸ”₯

So here's the tea: it checks the link, then figures out the current state by comparing what we advertise against what the link partner advertises. It's giving "who said what" detective work but for autonegotiation πŸ•΅οΈβ€β™€οΈ

this function is for Clause 37 1000Base-X mode β€” specifically that, no cap. don't come here expecting it to handle everything else, she's got a niche 🧚

If the link has changed, changed is set to true; false otherwise. Periodt. ⭐


🌈 SEE ALSO 🌈

okay so this is the part where the kernel flexes its whole friend group. the file itself is ./drivers/net/phy/phy_device.c β€” go say hi πŸ’œ

like, the whole PHY extended universe showed up to the group chat 😭πŸ”₯


✨ that's the whole page, bestie β€” mwah πŸ’‹

shoutout to the source directory ./drivers/net/phy, dated October 2026, from the Kernel API Manual itself. she's stamped, she's official, she's iconic πŸŽ€πŸ’–πŸ¦‹

πŸ“¦ where this page comes from