drivers/mcb/mcb-pci.c

File Facts

System

Linux kernel

Corpus path

drivers/mcb/mcb-pci.c

Extension

.c

Size

3554 bytes

Lines

158

Domain

Driver Families

Bucket

drivers/mcb

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/module.h
• linux/pci.h
• linux/mcb.h
• mcb-internal.h

Detected Declarations

• struct priv
• function mcb_pci_get_irq
• function mcb_pci_probe
• function mcb_pci_remove

Annotated Snippet

static struct pci_driver mcb_pci_driver = {
	.name = "mcb-pci",
	.id_table = mcb_pci_tbl,
	.probe = mcb_pci_probe,
	.remove = mcb_pci_remove,
};

module_pci_driver(mcb_pci_driver);

MODULE_AUTHOR("Johannes Thumshirn <johannes.thumshirn@men.de>");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("MCB over PCI support");
MODULE_IMPORT_NS("MCB");

Annotation

• Immediate include surface: `linux/module.h`, `linux/pci.h`, `linux/mcb.h`, `mcb-internal.h`.
• Detected declarations: `struct priv`, `function mcb_pci_get_irq`, `function mcb_pci_probe`, `function mcb_pci_remove`.
• Atlas domain: Driver Families / drivers/mcb.
• 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.