drivers/net/ethernet/freescale/enetc/enetc_pci_mdio.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/freescale/enetc/enetc_pci_mdio.c

Extension

.c

Size

3587 bytes

Lines

144

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/fsl/enetc_mdio.h
• linux/of_mdio.h
• enetc_pf.h

Detected Declarations

• function enetc_emdio_enable_err050089
• function enetc_emdio_disable_err050089
• function enetc_pci_mdio_probe
• function enetc_pci_mdio_remove
• export enetc_has_err050089

Annotated Snippet

static struct pci_driver enetc_pci_mdio_driver = {
	.name = KBUILD_MODNAME,
	.id_table = enetc_pci_mdio_id_table,
	.probe = enetc_pci_mdio_probe,
	.remove = enetc_pci_mdio_remove,
};
module_pci_driver(enetc_pci_mdio_driver);

MODULE_DESCRIPTION(ENETC_MDIO_DRV_NAME);
MODULE_LICENSE("Dual BSD/GPL");

Annotation

• Immediate include surface: `linux/fsl/enetc_mdio.h`, `linux/of_mdio.h`, `enetc_pf.h`.
• Detected declarations: `function enetc_emdio_enable_err050089`, `function enetc_emdio_disable_err050089`, `function enetc_pci_mdio_probe`, `function enetc_pci_mdio_remove`, `export enetc_has_err050089`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: pattern 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.