ice_check_ph...p_ready_e810(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

ice_check_phy_tx_tstamp_ready_e810 β€” bestie, this one just checks the Tx memory status register πŸŽ€

Oh and hey, we're in the Kernel API Manual today, not the normal user-facing one β€” different vibe, same queen energy πŸ‘‘


✨ SYNOPSIS ✨

int ice_check_phy_tx_tstamp_ready_e810 (struct ice_hw *hw );

🫢 ARGUMENTS 🫢

  • hw β€” pointer to the HW struct. that's it. that's the whole argument list, she's low maintenance πŸ’…

🌸 DESCRIPTION 🌸

okay so here's the tea, and it's honestly kind of iconic: the E810 devices do not have a Tx memory status register. like, at all. not a thing. it's giving "we forgot" but no, it's intentional πŸ¦‹

and ngl you should know this is intentionally different behavior from ice_get_phy_tx_tstamp_ready_e810, which always says that all bits are ready. so if you went in expecting these two to vibe the same way, they don't, and that was a whole choice ✨

this function gets called in cases where code will trigger interrupts if timestamps are waiting β€” so like, real consequences, not just for show 😭

and it should not be called for E810 hardware. fr fr. read that one twice, bestie πŸ’€

πŸ”₯ RETURN πŸ”₯

0.

that's it. that's the return value. zero. it said what it said πŸ‘‘


πŸ’œ SEE ALSO πŸ’œ

first up, the home base β€” the kernel file:

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

and now the full squad lmaooo she's got a lot of friends, get comfy πŸ“

the clock / source / timer crew:

e825c / e825 fam:

eth56g girlies (there's so many of them, love that for them) πŸ¦‹:

e82x crew:

e810 besties (our girl's own family πŸ’–):

e830 girlies:

the generic / core rotal family 🌈:

CGU / clock gen squad ⭐:


k that's the whole page bestie, you ate that 🫢 mwah πŸ’‹

source ./drivers/net/ethernet/intel/ice β€” October 2026 β€” that's the version/date stamp babes, no cap, go read it again if you need to 😭🌸
πŸ“¦ where this page comes from