e1000e_phc_...ncdevicetime(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ e1000e_phc_get_syncdevicetime ✨

okay so bestie, welcome to the Kernel API Manual πŸ’– this one is a callback β€” yes, a callback, main character energy fr β€” living in the e1000e driver, and it's the little guy the timekeeping code calls when it wants to know what time it is on both sides at once. πŸ•°οΈβœ¨


🌸 NAME 🌸

e1000e_phc_get_syncdevicetime β€” the callback you hand to the timekeeping code so it can read the system/device registers. that's it, that's the whole vibe πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int e1000e_phc_get_syncdevicetime (ktime_t *device , struct system_counterval_t *system , void *ctx );

πŸŽ€ ARGUMENTS πŸŽ€

  • device β€” the current device time, no cap. this is where the device's clock value goes 🫢
  • system β€” the system counter value read synchronously with device time. the whole point is that these two get read together, iykyk ⏱️
  • ctx β€” the context provided by timekeeping code. it's not yours, it's handed to you, just pass it along bestie πŸ™ˆ

⭐ DESCRIPTION ⭐

so what does it actually do? it reads the device clock and the system (ART) clock simultaneously β€” like, at the same time, together, holding hands 🀝 β€” and then returns the corrected clock values in ns (nanoseconds, the tiny tiny units πŸ’«).

that's the tea. simultaneous read, corrected values, nanoseconds. periodt. πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯


and that's the whole page, bestie!! πŸ«ΆπŸ’– this cutie came from ./drivers/net/ethernet/intel/e... β€” yes the path is literally truncated like that in the source, don't come for me 😭 β€” and it's dated October 2026. go read the other PTP pages, they're iconic too. slay, bye! πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from