drivers/dma/sa11x0-dma.c

File Facts

System

Linux kernel

Corpus path

drivers/dma/sa11x0-dma.c

Extension

.c

Size

27342 bytes

Lines

1099

Domain

Driver Families

Bucket

drivers/dma

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• 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/sched.h
• linux/device.h
• linux/dmaengine.h
• linux/init.h
• linux/interrupt.h
• linux/kernel.h
• linux/module.h
• linux/platform_device.h
• linux/slab.h
• linux/spinlock.h
• virt-dma.h

Detected Declarations

• struct sa11x0_dma_sg
• struct sa11x0_dma_desc
• struct sa11x0_dma_phy
• struct sa11x0_dma_chan
• struct sa11x0_dma_phy
• struct sa11x0_dma_dev
• struct sa11x0_dma_channel_desc
• function sa11x0_dma_free_desc
• function sa11x0_dma_start_desc
• function sa11x0_dma_start_sg
• function sa11x0_dma_complete
• function sa11x0_dma_irq
• function sa11x0_dma_start_txd
• function sa11x0_dma_tasklet
• function list_for_each_entry
• function sa11x0_dma_free_chan_resources
• function sa11x0_dma_pos
• function sa11x0_dma_tx_status
• function sa11x0_dma_issue_pending
• function for_each_sg
• function sa11x0_dma_device_config
• function sa11x0_dma_device_pause
• function sa11x0_dma_device_resume
• function sa11x0_dma_device_terminate_all
• function sa11x0_dma_filter_fn
• function sa11x0_dma_init_dmadev
• function sa11x0_dma_request_irq
• function sa11x0_dma_free_irq
• function sa11x0_dma_free_channels
• function list_for_each_entry_safe
• function sa11x0_dma_probe
• function sa11x0_dma_remove
• function sa11x0_dma_suspend
• function sa11x0_dma_resume
• function sa11x0_dma_init
• function sa11x0_dma_exit
• module init sa11x0_dma_init

Annotated Snippet

subsys_initcall(sa11x0_dma_init);

static void __exit sa11x0_dma_exit(void)
{
	platform_driver_unregister(&sa11x0_dma_driver);
}
module_exit(sa11x0_dma_exit);

MODULE_AUTHOR("Russell King");
MODULE_DESCRIPTION("SA-11x0 DMA driver");
MODULE_LICENSE("GPL v2");
MODULE_ALIAS("platform:sa11x0-dma");

Annotation

• Immediate include surface: `linux/sched.h`, `linux/device.h`, `linux/dmaengine.h`, `linux/init.h`, `linux/interrupt.h`, `linux/kernel.h`, `linux/module.h`, `linux/platform_device.h`.
• Detected declarations: `struct sa11x0_dma_sg`, `struct sa11x0_dma_desc`, `struct sa11x0_dma_phy`, `struct sa11x0_dma_chan`, `struct sa11x0_dma_phy`, `struct sa11x0_dma_dev`, `struct sa11x0_dma_channel_desc`, `function sa11x0_dma_free_desc`, `function sa11x0_dma_start_desc`, `function sa11x0_dma_start_sg`.
• Atlas domain: Driver Families / drivers/dma.
• Implementation status: integration 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.