genphy_c45_...t_get_status(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 genphy_c45_oatc14_cable_test_get_status(9) 🌸

okay so bestie, welcome to the Kernel API Manual entry for this absolute mouthful of a function. no cap, she's iconic, and she's here to check on an OATC14 10Base-T1S PHY cable test. periodt. πŸ’…


✨ NAME ✨

genphy_c45_oatc14_cable_test_get_status β€” Get status of OATC14 10Base-T1S PHY cable test.


🌈 SYNOPSIS 🌈

int genphy_c45_oatc14_cable_test_get_status (struct phy_device *phydev , bool *finished );

πŸŽ€ ARGUMENTS πŸŽ€

  • phydev β€” pointer to the PHY device structure
  • finished β€” pointer to a boolean set true if the test is complete

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so this function retrieves the current status of the OATC14 10Base-T1S PHY cable test. it reads the OATC14 HDD register to figure out whether the test results are valid and whether the test has finished. main character energy fr fr. πŸ’–

if the test is complete, the function reports the cable test result via the ethtool cable test interface using ethnl_cable_test_result, and then clears the test control bit in the PHY register to reset the test state. slay. ✨


πŸ’€ RETURN πŸ’€

0 on success, or a negative error code on failure (e.g. register read/write error). no cap, that error code can absolutely ruin the vibe. 😭


πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file in question is ./drivers/net/phy/phy-c45.c, and here's the whole function squad:


xoxo, your Kernel API Manual bestie πŸ’Œ β€” this page comes from source path ./drivers/net/phy, dated October 2026, and the footer title is genphy_c45_...t_get_status(9). byeee 🫢
πŸ“¦ where this page comes from