e1000e_phc_...ncdevicetime(9)
β¨ 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 π₯
- Kernel file
./drivers/net/ethernet/intel/e1000e/ptp.c e1000e_phc_adjfine(9)e1000e_phc_adjtime(9)e1000e_phc_getcrosststamp(9)e1000e_phc_gettimex(9)e1000e_phc_settime(9)e1000e_phc_enable(9)e1000e_ptp_init(9)e1000e_ptp_remove(9)
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
- 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