drivers/mmc/host/dw_mmc-pci.c
Source file repositories/reference/linux-study-clean/drivers/mmc/host/dw_mmc-pci.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/mmc/host/dw_mmc-pci.c- Extension
.c- Size
- 2218 bytes
- Lines
- 96
- Domain
- Driver Families
- Bucket
- drivers/mmc
- 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/interrupt.hlinux/module.hlinux/io.hlinux/irq.hlinux/pci.hlinux/pci-epf.hlinux/pm_runtime.hlinux/slab.hlinux/mmc/host.hlinux/mmc/mmc.hdw_mmc.hdw_mmc-pltfm.h
Detected Declarations
function dw_mci_pci_probefunction dw_mci_pci_remove
Annotated Snippet
static struct pci_driver dw_mci_pci_driver = {
.name = "dw_mmc_pci",
.id_table = dw_mci_pci_id,
.probe = dw_mci_pci_probe,
.remove = dw_mci_pci_remove,
.driver = {
.pm = pm_ptr(&dw_mci_pmops),
},
};
module_pci_driver(dw_mci_pci_driver);
MODULE_DESCRIPTION("DW Multimedia Card PCI Interface driver");
MODULE_AUTHOR("Shashidhar Hiremath <shashidharh@vayavyalabs.com>");
MODULE_LICENSE("GPL v2");
Annotation
- Immediate include surface: `linux/interrupt.h`, `linux/module.h`, `linux/io.h`, `linux/irq.h`, `linux/pci.h`, `linux/pci-epf.h`, `linux/pm_runtime.h`, `linux/slab.h`.
- Detected declarations: `function dw_mci_pci_probe`, `function dw_mci_pci_remove`.
- Atlas domain: Driver Families / drivers/mmc.
- 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.