drivers/net/ethernet/cadence/macb_pci.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/cadence/macb_pci.c

Extension

.c

Size

3468 bytes

Lines

136

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/clk.h
• linux/clk-provider.h
• linux/etherdevice.h
• linux/module.h
• linux/pci.h
• linux/platform_device.h
• macb.h

Detected Declarations

• function Copyright
• function macb_remove

Annotated Snippet

static struct pci_driver macb_pci_driver = {
	.name     = PCI_DRIVER_NAME,
	.id_table = dev_id_table,
	.probe    = macb_probe,
	.remove	  = macb_remove,
};

module_pci_driver(macb_pci_driver);
MODULE_DEVICE_TABLE(pci, dev_id_table);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Cadence NIC PCI wrapper");

Annotation

• Immediate include surface: `linux/clk.h`, `linux/clk-provider.h`, `linux/etherdevice.h`, `linux/module.h`, `linux/pci.h`, `linux/platform_device.h`, `macb.h`.
• Detected declarations: `function Copyright`, `function macb_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.