phy_has_rxtstamp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– phy_has_rxtstamp(9) β€” the "does this PHY do receive timestamps" check πŸ’–

okay so bestie, this is a page from the Kernel API Manual, and it's a little one β€” literally a single yes/no question wrapped in a function. but it's a very important yes/no question, so let's get into it 🫢


✨ NAME ✨

phy_has_rxtstamp β€” literally just tests whether a PHY supports receive time stamping. that's it. that's the whole vibe check. ⏱️


πŸ¦‹ SYNOPSIS πŸ¦‹

bool phy_has_rxtstamp (struct phy_device *phydev );

returns a bool, takes a pointer, no drama. iconic behavior, honestly. πŸ‘‘


🌸 ARGUMENTS 🌸

  • phydev β€” the phy_device struct. that's the one and only thing you hand over. she's the main character here, the PHY we're asking about 🧚

🌈 SEE ALSO 🌈

so there's a whole friend group here, and the kernel file it all lives in is ./include/linux/phy.h β€” go say hi to the whole fam:

like, it's giving "who's who of the PHY universe" πŸ’… and yes, phy_has_txtstamp(9) is right there too β€” the transmit-side sibling, iykyk.


πŸŽ€ tiny note bestie: this page is short because the function is short. no options, no env vars, no exit statuses, no bugs section, no author block. don't go looking for them, they're not hiding. πŸ™ˆ

and that's the whole page, bestie! 🌟 straight out of ./include/linux, dated October 2026, and that's the Kernel API Manual signing off β€” mwah, go timestamp some packets responsibly πŸ’œπŸ”₯

πŸ“¦ where this page comes from