phy_caps_linkmode_max_speed(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… phy_caps_linkmode_max_speed β€” the Kernel API Manual, section 9, bestie ✨

Okay so real quick: this page lives in the Kernel API Manual, section 9, and the star of the show is phy_caps_linkmode_max_speed. Yes it's a long name. No we're not shortening it. It's iconic and it earned it. πŸŽ€


✨ NAME ✨

phy_caps_linkmode_max_speed β€” clamp a linkmodes set to a max speed. That's it, that's the whole vibe: you hand it a set of linkmodes, you hand it a ceiling, and it clamps. Like a bouncer for speeds. πŸšͺπŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void phy_caps_linkmode_max_speed (u32 max_speed , unsigned long
*linkmodes );

Two arguments, zero return value (it's void, ngl it gives nothing back and that's on purpose). 🫢


🌸 ARGUMENTS 🌸

  • max_speed β€” the speed limit for the linkmode set. Think of it as the ceiling, the cap, the "you shall not pass" number. Anything spicier than this gets clipped. πŸ”₯
  • linkmodes β€” the linkmodes to limit. This is the set getting clamped, fr fr. It's an unsigned long * pointer, so yes, it's getting modified in place. πŸ‘‘

πŸ‘‘ SEE ALSO πŸ‘‘

If you wanna go deeper (and honestly? you should, it's giving main character energy), this all lives in the kernel file ./drivers/net/phy/phy_caps.c, and it's besties with the whole crew:

That's the whole group chat, no cap. πŸ“‹βœ¨


Heads up bestie: every single one of those is a real reference, so if you're going linkmode-coded, read them all before you start guessing at behaviour. I said what I said. πŸ’€

And that's the page! Sourced from ./drivers/net/phy, dated October 2026, filed under phy_caps_linkmode_max_speed(9). Slay, go clamp some speeds, mwah πŸ’–πŸ§šβ­

πŸ“¦ where this page comes from