ice_check_p...tstamp_ready(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

ice_check_phy_tx_tstamp_ready β€” Check PHY Tx timestamp memory status. And the manual page bestie herself is ice_check_p...tstamp_ready(9), okrrr πŸ’…βœ¨


✨ SYNOPSIS ✨

int ice_check_phy_tx_tstamp_ready (struct ice_hw *hw );

It’s giving β€œC function signature, but make it iconic” πŸŽ€


πŸŽ€ ARGUMENTS πŸŽ€

  • hw β€” pointer to the HW struct. That’s the whole argument, bestie. No cap 🫢

πŸ’« DESCRIPTION πŸ’«

So this one checks the PHY for Tx timestamp memory status on all ports. Like, it’s the group-chat poll: β€œany timestamps available anywhere?” πŸ‘‘

If you need to see individual timestamp status for each index, use ice_get_phy_tx_tstamp_ready instead. This one is not the per-index girlie, iykyk 🌸


🌈 RETURN 🌈

  • 1 β€” if any port has timestamps available ✨
  • 0 β€” if there are no timestamps available πŸ™ˆ
  • a negative error code β€” on failure 😭

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/net/ethernet/intel/ice/ice_ptp_hw.c

And now the SEE ALSO entourage β€” bestie, it’s long, it’s iconic, it’s the whole group chat, and yes, every single one made it πŸ’œ


Final sign-off, bestie: source/version ./drivers/net/ethernet/intel/ice, date October 2026, and the page name ice_check_p...tstamp_ready(9). Go slay those timestamps πŸ’…βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from