phy_start_aneg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€ β€” phy_start_aneg(9) from the Kernel API Manual

okay so bestie, this page is phy_start_aneg(9), and the name line says phy_start_aneg β€” start auto-negotiation for this PHY device. It's giving "we're starting auto-negotiation for this PHY device," and I'm obsessed. πŸ’–

⚑ SYNOPSIS ⚑

it's literally this signature, copy it exactly:

int phy_start_aneg (struct phy_device *phydev );

🫢 ARGUMENTS 🫢

one argument, periodt:

  • phydev β€” the phy_device struct. That's the whole guest list, bestie. 🫢

πŸ’« DESCRIPTION πŸ’«

okay so here's the tea: it sanitizes the settings (if we're not autonegotiating them β€” iykyk), and then it calls the driver's config_aneg function. If the PHYCONTROL Layer is operating, the state gets changed to reflect the beginning of Auto-negotiation or forcing. No cap, that's the whole flow. ✨

🌈 SEE ALSO 🌈

Kernel file ./drivers/net/phy/phy.c is the home base, and the rest of the friend group is literally right here:

Signing off from source/version ./drivers/net/phy, dated October 2026 β€” phy_start_aneg(9), Kernel API Manual, byeee bestie πŸ’…βœ¨
πŸ“¦ where this page comes from