drivers/net/mdio/mdio-thunder.c

File Facts

System

Linux kernel

Corpus path

drivers/net/mdio/mdio-thunder.c

Extension

.c

Size

3507 bytes

Lines

149

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.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/acpi.h
• linux/gfp.h
• linux/io.h
• linux/module.h
• linux/of_address.h
• linux/of_mdio.h
• linux/pci.h
• linux/phy.h
• mdio-cavium.h

Detected Declarations

• struct thunder_mdiobus_nexus
• function thunder_mdiobus_pci_probe
• function thunder_mdiobus_pci_remove

Annotated Snippet

static struct pci_driver thunder_mdiobus_driver = {
	.name = KBUILD_MODNAME,
	.id_table = thunder_mdiobus_id_table,
	.probe = thunder_mdiobus_pci_probe,
	.remove = thunder_mdiobus_pci_remove,
};

module_pci_driver(thunder_mdiobus_driver);

MODULE_DESCRIPTION("Cavium ThunderX MDIO bus driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/gfp.h`, `linux/io.h`, `linux/module.h`, `linux/of_address.h`, `linux/of_mdio.h`, `linux/pci.h`, `linux/phy.h`.
• Detected declarations: `struct thunder_mdiobus_nexus`, `function thunder_mdiobus_pci_probe`, `function thunder_mdiobus_pci_remove`.
• 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.