viortc_ptp_do_xtstamp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ viortc_ptp_do_xtstamp πŸ’«

okay bestie, welcome to the viortc_ptp_do_xtstamp(9) page β€” it's a kernel API manual entry and it's literally the whole vibe of "hey device, gimme a crosststamp please" 🫢


🌸 NAME 🌸

viortc_ptp_do_xtstamp β€” get crosststamp from device ✨


πŸŽ€ SYNOPSIS πŸŽ€

int viortc_ptp_do_xtstamp (struct viortc_ptp_clock *vio_ptp , u8
hw_counter , enum clocksource_ids cs_id , struct viortc_ptp_cross_ctx
*ctx );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • vio_ptp β€” the virtio_rtc PTP clock, aka the main character of this whole situation πŸ‘‘
  • hw_counter β€” the virtio_rtc HW counter type, it's a u8, slay πŸ’…
  • cs_id β€” the clocksource id that corresponds to hw_counter, no cap they're a matched set πŸŽ€
  • ctx β€” the context for get_device_system_crosststamp, keeping it all organized fr fr

πŸ’– DESCRIPTION πŸ’–

Reads the HW-specific crosststamp from the device. That's it. That's the whole plot. it's giving "just go ask the hardware nicely" 😭✨


⭐ CONTEXT ⭐

Process context. so like, normal sleepable vibes, not some interrupt-y chaos πŸ™ˆ


🌈 RETURN 🌈

  • Zero on success πŸŽ‰
  • negative error code otherwise πŸ’€

πŸ”₯ SEE ALSO πŸ”₯


ok that's the whole page bestie, go read the source and hydrate πŸ’œ

sign-off szn πŸŽ€ β€” this one's from the ./drivers/virtio source tree, dated October 2026, and you can find it filed under viortc_ptp_do_xtstamp(9) in the Kernel API Manual. obsessed. periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from