drivers/dma/hsu/pci.c

File Facts

System

Linux kernel

Corpus path

drivers/dma/hsu/pci.c

Extension

.c

Size

3307 bytes

Lines

136

Domain

Driver Families

Bucket

drivers/dma

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.
• 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/bitops.h
• linux/device.h
• linux/interrupt.h
• linux/module.h
• linux/pci.h
• hsu.h

Detected Declarations

• function Copyright
• function hsu_pci_dma_remove
• function hsu_pci_probe

Annotated Snippet

static struct pci_driver hsu_pci_driver = {
	.name		= "hsu_dma_pci",
	.id_table	= hsu_pci_id_table,
	.probe		= hsu_pci_probe,
};

module_pci_driver(hsu_pci_driver);

MODULE_LICENSE("GPL v2");
MODULE_DESCRIPTION("High Speed UART DMA PCI driver");
MODULE_AUTHOR("Andy Shevchenko <andriy.shevchenko@linux.intel.com>");

Annotation

• Immediate include surface: `linux/bitops.h`, `linux/device.h`, `linux/interrupt.h`, `linux/module.h`, `linux/pci.h`, `hsu.h`.
• Detected declarations: `function Copyright`, `function hsu_pci_dma_remove`, `function hsu_pci_probe`.
• Atlas domain: Driver Families / drivers/dma.
• Implementation status: pattern implementation candidate.
• 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.