dp83td510_c...t_tdr_status(9)
π dp83td510_cable_test_get_tdr_status(9) π
ok so this is a page straight out of the Kernel API Manual (yes, the actual kernel docs, we're fancy now) and it's all about dp83td510_cable_test_get_tdr_status β the little function that tells you how the TDR test on the DP83TD510 PHY is going. bestie, let's get into it β¨
πΈ NAME πΈ
dp83td510_cable_test_get_tdr_status β ngl this one does exactly what it says on the tin: it gets the status of the TDR test for the DP83TD510 PHY π
π¦ SYNOPSIS π¦
int dp83td510_cable_test_get_tdr_status (struct phy_device *phydev ,
bool *finished );
it's giving "small function, big responsibility" tbh π
π DESCRIPTION π
okay so here's the whole vibe: this function sets the finished flag to true if the test is complete. that's it, that's the tea π like yes, that's literally the entire job and it ate, no notes.
β¨ ARGUMENTS β¨
phydevβ pointer to thephy_devicestructure. your main character struct, the one holding all the PHY lore πfinishedβ pointer to a boolean that indicates whether the test is finished. it's the little flag that tells you "we're so done here" π
π₯ RETURN π₯
0 on success, or a negative error code on failure π so like, if it's not 0, something went sideways, and that's your sign to go look.
π SEE ALSO π
- Kernel file
./drivers/net/phy/dp83td510.c dp83td510_update_stats(9)dp83td510_cable_test_start(9)dp83td510_cable_test_get_alcd_status(9)dp83td510_cable_test_get_status(9)
the whole friend group fr fr, go read their pages too π«Ά
aaaand that's the page!! π this gem lives over in ./drivers/net/phy and it's dated October 2026 β iconic, timeless, slay. mwah πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms