drivers/net/ethernet/marvell/octeontx2/nic/otx2_ptp.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/marvell/octeontx2/nic/otx2_ptp.h

Extension

.h

Size

707 bytes

Lines

33

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

• No C-style include directives detected by the generator.

Detected Declarations

• function Copyright
• function otx2_ptp_convert_tx_timestamp
• function cn10k_ptp_convert_timestamp

Annotated Snippet

#ifndef OTX2_PTP_H
#define OTX2_PTP_H

static inline u64 otx2_ptp_convert_rx_timestamp(u64 timestamp)
{
	return be64_to_cpu(*(__be64 *)&timestamp);
}

static inline u64 otx2_ptp_convert_tx_timestamp(u64 timestamp)
{
	return timestamp;
}

static inline u64 cn10k_ptp_convert_timestamp(u64 timestamp)
{
	return ((timestamp >> 32) * NSEC_PER_SEC) + (timestamp & 0xFFFFFFFFUL);
}

int otx2_ptp_init(struct otx2_nic *pfvf);
void otx2_ptp_destroy(struct otx2_nic *pfvf);

int otx2_ptp_clock_index(struct otx2_nic *pfvf);
int otx2_ptp_tstamp2time(struct otx2_nic *pfvf, u64 tstamp, u64 *tsns);

#endif

Annotation

• Detected declarations: `function Copyright`, `function otx2_ptp_convert_tx_timestamp`, `function cn10k_ptp_convert_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.