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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

1600 bytes

Lines

48

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• iavf_types.h

Detected Declarations

• function iavf_ptp_init
• function iavf_virtchnl_send_ptp_cmd
• function iavf_ptp_extend_32b_timestamp

Annotated Snippet

static inline void iavf_ptp_init(struct iavf_adapter *adapter) { }
static inline void iavf_ptp_release(struct iavf_adapter *adapter) { }
static inline void iavf_ptp_process_caps(struct iavf_adapter *adapter) { }
static inline bool iavf_ptp_cap_supported(const struct iavf_adapter *adapter,
					  u32 cap)
{
	return false;
}

static inline void iavf_virtchnl_send_ptp_cmd(struct iavf_adapter *adapter) { }
static inline int iavf_ptp_set_ts_config(struct iavf_adapter *adapter,
					 struct kernel_hwtstamp_config *config,
					 struct netlink_ext_ack *extack)
{
	return -1;
}

static inline u64 iavf_ptp_extend_32b_timestamp(u64 cached_phc_time,
						u32 in_tstamp)
{
	return 0;
}

#endif /* IS_ENABLED(CONFIG_PTP_1588_CLOCK) */
#endif /* _IAVF_PTP_H_ */

Annotation

• Immediate include surface: `iavf_types.h`.
• Detected declarations: `function iavf_ptp_init`, `function iavf_virtchnl_send_ptp_cmd`, `function iavf_ptp_extend_32b_timestamp`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.