idpf_ptp_is...x_tstamp_ena(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– idpf_ptp_is_vport_rx_tstamp_ena β€” the Kernel API Manual glow-up ✨

okay so bestie, we are in the Kernel API Manual today and the function we're stanning is idpf_ptp_is_vport_rx_tstamp_ena. yes the header got chopped to idpf_ptp_is...x_tstamp_ena(9) because the terminal is a hater, but the full name is right there and it ate. let's get into it πŸŽ€

🌸 NAME 🌸

idpf_ptp_is_vport_rx_tstamp_ena β€” literally just verifying whether Rx timestamping is enabled for a given vport. that's the whole gig. no cap. πŸ¦‹

✨ SYNOPSIS ✨

bool idpf_ptp_is_vport_rx_tstamp_ena(struct idpf_vport *vport);

πŸŽ€ ARGUMENTS πŸŽ€

  • vport β€” the virtual port structure. that's the one you're asking about, bestie πŸ’…

πŸ’« DESCRIPTION πŸ’«

so here's the tea β˜•: the Rx timestamp feature is considered enabled only if two things line up, and lowkey they're a package deal:

  • the PTP clock for the adapter is created, and
  • it's actually possible to read the value of the device clock.

and why do we care about that second one, you ask? because (and this is the important bit, don't skip it πŸ™ˆ) the Rx timestamp value needs to get extended to 64 bit based on the current device clock time. so if you can't read the clock, you can't extend, and the whole vibe check fails. it's giving "you can't sit with us unless you can tell time." ⏰

πŸ”₯ RETURN πŸ”₯

  • true if the Rx timestamping is enabled πŸ’–
  • false otherwise πŸ’€

🌈 SEE ALSO 🌈

okay this is the friend group, all of them iconic, all of them in Kernel file ./drivers/net/ethernet/intel/idpf/idpf_ptp.h:

  • struct idpf_ptp_cmd(9)
  • enum idpf_ptp_access(9)
  • struct idpf_ptp_secondary_mbx(9)
  • enum idpf_ptp_tx_tstamp_state(9)
  • struct idpf_ptp_tx_tstamp_status(9)
  • struct idpf_ptp_tx_tstamp(9)
  • struct idpf_ptp_vport_tx_tstamp_caps(9)
  • struct idpf_ptp(9)
  • idpf_ptp_info_to_adapter(9)
  • struct idpf_ptp_dev_timers(9)
  • idpf_ptp_is_vport_tx_tstamp_ena(9)

and that's the page, bestie!! 🫢 this came to you from ./drivers/net/ethernet/intel/idpf, dated October 2026, and it's the idpf_ptp_is...x_tstamp_ena(9) man page being its full self. go read a clock, stay hydrated, mwah πŸ’œβœ¨

πŸ“¦ where this page comes from