idpf_ptp_ge...tstamps_caps(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– idpf_ptp_get_vport_tstamps_caps πŸ’–

okay bestie, so this one's from the Kernel API Manual (yes, the actual kernel docs, we're fancy now ✨) and it's literally just... asking the hardware what timestamp stuff it can do. no biggie. let's get into it 🫢


✨ NAME ✨

idpf_ptp_get_vport_tstamps_caps β€” the function that sends a virtchnl message to grab the timestamp capabilities for a vport πŸ’…


🌸 SYNOPSIS 🌸

int idpf_ptp_get_vport_tstamps_caps(struct idpf_vport *vport);

πŸŽ€ ARGUMENTS πŸŽ€

  • vport β€” the virtual port structure. yeah. that's the whole argument list. she's low maintenance πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

So basically what happens is: this function sends the virtchnl get vport tstamps caps message, and what comes back is the set of tstamp capabilities for that specific vport. like, per-vport. each one gets its own. no sharing, no cap 🧚

that's it. that's the whole description. iconic brevity honestly πŸ‘‘


⭐ RETURN ⭐

  • 0 on success β€” slay, we love a clean zero πŸ’š
  • -errno otherwise β€” not slay, something went sideways, and the error code comes back negative as is the convention 😭

πŸ”₯ SEE ALSO πŸ”₯

Kernel file: ./drivers/net/ethernet/intel/idpf/idpf_virtchnl_ptp.c β€” that's where she lives, bestie, go read the source πŸ“‚

and the whole PTP friend group, in the order the page lists them:


ngl if you're messing with timestamps on intel idpf NICs, you're gonna be seeing a lot of these idpf_ptp_* functions. consider this your new group chat πŸ’€πŸ’œ

<div align="center">✧ο½₯゚: okay that's the whole page, bestie :ο½₯゚✧</div>

sourced straight from ./drivers/net/ethernet/intel/idpf, dated October 2026, and filed under that truncated little header idpf_ptp_ge...tstamps_caps(9) because the man page gods ran out of horizontal space πŸ˜­πŸ’– go forth and timestamp responsibly πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from