phy_get_rate_matching(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… phy_get_rate_matching β€” a Kernel API Manual moment

okay so bestie, welcome to phy_get_rate_matching(9) β€” literally the glow-up check for whether your phy can do rate matching. it's a whole vibe, i promise. (this one lives in the Kernel API Manual, just so u know what u signed up for 🫢)


✨ NAME ✨

phy_get_rate_matching β€” figure out if rate matching is even a thing this phy supports, no cap


πŸ¦‹ SYNOPSIS πŸ¦‹

int phy_get_rate_matching (struct phy_device *phydev , phy_interface_t
iface );

like, that's the whole signature. she's short but she's serving πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • phydev β€” the phy device we're getting rate matching info for. ur main character 🌟
  • iface β€” the interface mode to use. the vibe we're checking against ✨

🌸 DESCRIPTION 🌸

so what she does is: this determines the type of rate matching (if any 😭) that the phy supports using iface.

and here's the cute part β€” iface may be PHY_INTERFACE_MODE_NA to determine if any interface supports rate matching. yes bestie, she'll check around for u πŸ‘‘ lowkey a wingwoman.


πŸ’– RETURN πŸ’–

she returns the type of rate matching the phy supports for iface, or RATE_MATCH_NONE if there's nothing there. no crumbs. πŸ’€


🌈 SEE ALSO 🌈

okay this is the part where the group chat goes off, because there are SO many siblings. all of these are in the kernel file ./drivers/net/phy/phy.c, and honestly? iconic lineup:

like… that's the whole friend group fr fr 🧚


ok and the lil sign-off at the bottom of the page says she comes from ./drivers/net/phy, dated October 2026, in the Kernel API Manual. so she's a certified kernel girlie with receipts πŸ’œ periodt.
πŸ“¦ where this page comes from