drivers/net/phy/mscc/mscc_ptp.h

File Facts

System

Linux kernel

Corpus path

drivers/net/phy/mscc/mscc_ptp.h

Extension

.h

Size

20093 bytes

Lines

474

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

• struct vsc85xx_ptphdr
• struct vsc85xx_ts_fifo
• struct vsc85xx_ptp
• enum ptp_cmd

Annotated Snippet

struct vsc85xx_ptphdr {
	u8 tsmt; /* transportSpecific | messageType */
	u8 ver;  /* reserved0 | versionPTP */
	__be16 msglen;
	u8 domain;
	u8 rsrvd1;
	__be16 flags;
	__be64 correction;
	__be32 rsrvd2;
	__be64 clk_identity;
	__be16 src_port_id;
	__be16 seq_id;
	u8 ctrl;
	u8 log_interval;
} __attribute__((__packed__));

/* Represents an entry in the timestamping FIFO */
struct vsc85xx_ts_fifo {
	u32 ns;
	u64 secs:48;
	u8 sig[16];
} __attribute__((__packed__));

struct vsc85xx_ptp {
	struct phy_device *phydev;
	struct ptp_clock *ptp_clock;
	struct ptp_clock_info caps;
	struct sk_buff_head tx_queue;
	enum hwtstamp_tx_types tx_type;
	enum hwtstamp_rx_filters rx_filter;
	u8 configured:1;
};

#endif /* _MSCC_PHY_PTP_H_ */

Annotation

• Detected declarations: `struct vsc85xx_ptphdr`, `struct vsc85xx_ts_fifo`, `struct vsc85xx_ptp`, `enum ptp_cmd`.
• 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.