drivers/mmc/host/cavium-thunderx.c

File Facts

System

Linux kernel

Corpus path

drivers/mmc/host/cavium-thunderx.c

Extension

.c

Size

5037 bytes

Lines

205

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/device.h
• linux/dma-mapping.h
• linux/interrupt.h
• linux/mmc/mmc.h
• linux/module.h
• linux/of.h
• linux/of_platform.h
• linux/platform_device.h
• linux/pci.h
• cavium.h

Detected Declarations

• function Copyright
• function thunder_mmc_release_bus
• function thunder_mmc_int_enable
• function thunder_mmc_register_interrupts
• function thunder_mmc_probe
• function for_each_child_of_node
• function thunder_mmc_remove

Annotated Snippet

static struct pci_driver thunder_mmc_driver = {
	.name = KBUILD_MODNAME,
	.id_table = thunder_mmc_id_table,
	.probe = thunder_mmc_probe,
	.remove = thunder_mmc_remove,
};

module_pci_driver(thunder_mmc_driver);

MODULE_AUTHOR("Cavium Inc.");
MODULE_DESCRIPTION("Cavium ThunderX eMMC Driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/device.h`, `linux/dma-mapping.h`, `linux/interrupt.h`, `linux/mmc/mmc.h`, `linux/module.h`, `linux/of.h`, `linux/of_platform.h`, `linux/platform_device.h`.
• Detected declarations: `function Copyright`, `function thunder_mmc_release_bus`, `function thunder_mmc_int_enable`, `function thunder_mmc_register_interrupts`, `function thunder_mmc_probe`, `function for_each_child_of_node`, `function thunder_mmc_remove`.
• Atlas domain: Driver Families / drivers/mmc.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.