genphy_c45_..._get_sqi_max(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… genphy_c45_..._get_sqi_max(9) πŸ’…

okay so bestie, this little icon lives in the Kernel API Manual and it's all about asking a PHY how good its vibes can possibly get. yes we're talking Signal Quality. yes it's as cute as it sounds. let's go 🫢


✨ NAME ✨

genphy_c45_oatc14_get_sqi_max β€” literally just "Get maximum supported SQI or SQI+ level of OATC14 10Base-T1S PHY". that's the whole job. she gets the max. she's a getter. queen behavior πŸ‘‘


🌸 SYNOPSIS 🌸

int genphy_c45_oatc14_get_sqi_max (struct phy_device *phydev );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • phydev β€” pointer to the phy_device structure. that's the PHY device in question, our main character for this function πŸ’–

πŸ”₯ DESCRIPTION πŸ”₯

so what does she do. this function returns the maximum supported Signal Quality Indicator (SQI) β€” or the SQI+ level, if that's the flavor we're in. the way that it just hands you the ceiling of how good your signal quality readout can go. iconic.

one tiny detail that's lowkey important: the SQI capability gets updated on first invocation β€” but only if it hasn't already been updated. so first call does the little housekeeping, and after that she already knows and doesn't need to redo it. efficient! we stan ✨


⭐ RETURN ⭐

  • Maximum SQI/SQI+ level supported πŸ’–
  • Negative errno on capability read failure 😭 (yeah, if the capability read flops, you get a negative errno. sad but honest)

🌈 SEE ALSO 🌈

the besties!! the whole group chat!! the kernel file is ./drivers/net/phy/phy-c45.c and here's everyone she hangs out with:

like, that's the whole friend group. no cap, go read them too 🧚


quick reminder bestie: this page is from ./drivers/net/phy, dated October 2026, and the page itself is genphy_c45_..._get_sqi_max(9). mwah πŸ’‹ πŸŽ€
πŸ“¦ where this page comes from