iavf_ptp_cap_supported(9)

📦 version 7.3.1, in nixpkgs unstable

💅 iavf_ptp_cap_supported(9) — the kernel API manual, but make it make sense

okay so bestie, welcome to the Kernel API Manual page for iavf_ptp_cap_supported, and honestly? it's a little baddie of a function. tiny, does exactly one thing, does it well. we love a focused icon. ✨

🌸 NAME 🌸

iavf_ptp_cap_supported — literally just checks if a PTP capability is supported. that's it. that's the whole vibe. 🎀

✨ SYNOPSIS ✨

bool iavf_ptp_cap_supported (const struct iavf_adapter *adapter , u32
cap );

like, yes, the line wraps weird in the original and we're keeping it, no notes. 💅

🦋 ARGUMENTS 🦋

  • adapter — the private adapter structure. it's giving "main character struct", it holds everything, just hand it over. 🫶
  • cap — the capability bitmask you wanna check. bitmasks are so underrated fr fr. ⭐

🔥 RETURN 🔥

it comes back with true if every capability set in cap is also set in the enabled capabilities reported by the PF. and bestie, note the word every — this is an all-or-nothing situation, not a "one of these is fine" situation. if even one bit in cap isn't enabled by the PF, you get false. no partial credit, no half-slay. 😭

lowkey important: it's checking against the enabled capabilities reported by the PF — not against whatever you wish were enabled. the PF said what it said. 🙈

👑 SEE ALSO 👑

the kernel file lives here, exactly this path, don't @ me:

./drivers/net/ethernet/intel/iavf/iavf_ptp.c

and the whole friend group, in order, because they all show up together:

and that's the page, bestie, go check some capabilities 🧚💜

source path: ./drivers/net/ethernet/intel/iavf · dated October 2026 · and yes, the page itself is called iavf_ptp_cap_supported(9) — that's the whole sign-off, mwah 💋🌈

📦 where this page comes from