include/linux/pcs/pcs-xpcs.h

File Facts

System

Linux kernel

Corpus path

include/linux/pcs/pcs-xpcs.h

Extension

.h

Size

1635 bytes

Lines

64

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/clk.h
• linux/fwnode.h
• linux/mdio.h
• linux/phy.h
• linux/phylink.h
• linux/types.h

Detected Declarations

• struct dw_xpcs_info
• struct dw_xpcs
• enum dw_xpcs_pcs_id
• enum dw_xpcs_pma_id

Annotated Snippet

struct dw_xpcs_info {
	u32 pcs;
	u32 pma;
};

struct dw_xpcs;

struct phylink_pcs *xpcs_to_phylink_pcs(struct dw_xpcs *xpcs);
int xpcs_get_an_mode(struct dw_xpcs *xpcs, phy_interface_t interface);
void xpcs_config_eee_mult_fact(struct dw_xpcs *xpcs, u8 mult_fact);
struct dw_xpcs *xpcs_create_mdiodev(struct mii_bus *bus, int addr);
struct dw_xpcs *xpcs_create_fwnode(struct fwnode_handle *fwnode);
void xpcs_destroy(struct dw_xpcs *xpcs);

struct phylink_pcs *xpcs_create_pcs_mdiodev(struct mii_bus *bus, int addr);
void xpcs_destroy_pcs(struct phylink_pcs *pcs);

#endif /* __LINUX_PCS_XPCS_H */

Annotation

• Immediate include surface: `linux/clk.h`, `linux/fwnode.h`, `linux/mdio.h`, `linux/phy.h`, `linux/phylink.h`, `linux/types.h`.
• Detected declarations: `struct dw_xpcs_info`, `struct dw_xpcs`, `enum dw_xpcs_pcs_id`, `enum dw_xpcs_pma_id`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.