idpf_ptp_get...sync_handler(9)
π idpf_ptp_get_tx_tstamp_async_handler π
okay so this is the page for idpf_ptp_get_tx_tstamp_async_handler, filed under idpf_ptp_get...sync_handler(9) in the Kernel API Manual β section 9, kernel API, you know the drill π
β¨ NAME β¨
idpf_ptp_get_tx_tstamp_async_handler β the async callback for getting Tx tstamps, bestie π
π¦ SYNOPSIS π¦
void idpf_ptp_get_tx_tstamp_async_handler (void *ctx , struct kvec *mem , int status );
that's the whole vibe. void, three args, no notes β¨
πΈ ARGUMENTS πΈ
ctxβ the adapter pointer π«Άmemβ the address and size of the responsestatusβ the return value of the request
π DESCRIPTION π
so what it does: it reads the tstamps Tx tstamp values out of a received message and drops them directly into the skb. the way that's efficient?? iconic π₯
and how many timestamps are we reading? the virtchnl message decides that β it specifies the number, not us. periodt π
β RETURN β
0 on success, -errno otherwise π (yes the synopsis says void, and yes this page still lists a return. we're keeping it exactly as written, don't come for me π)
π SEE ALSO π
- the kernel file itself, no cap:
./drivers/net/ethernet/intel/idpf/idpf_virtchnl_ptp.cπ idpf_ptp_get_caps(9)idpf_ptp_get_dev_clk_time(9)idpf_ptp_get_cross_time(9)idpf_ptp_set_dev_clk_time(9)idpf_ptp_adj_dev_clk_time(9)idpf_ptp_adj_dev_clk_fine(9)idpf_ptp_get_vport_tstamps_caps(9)idpf_ptp_update_tstamp_tracker(9)idpf_ptp_get_tstamp_value(9)idpf_ptp_get_tx_tstamp(9)
like a whole friend group of ptp functions, and honestly? obsessed π§
and that's the page!! source + version vibes: ./drivers/net/ethernet/intel/idpf, dated October 2026 β go off, kernel docs ππ
π¦ 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