drivers/dma/ti/omap-dma.c

File Facts

System

Linux kernel

Corpus path

drivers/dma/ti/omap-dma.c

Extension

.c

Size

48325 bytes

Lines

1959

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/cpu_pm.h
• linux/delay.h
• linux/dmaengine.h
• linux/dma-mapping.h
• linux/dmapool.h
• linux/err.h
• linux/init.h
• linux/interrupt.h
• linux/list.h
• linux/module.h
• linux/omap-dma.h
• linux/platform_device.h
• linux/slab.h
• linux/spinlock.h
• linux/of.h
• linux/of_dma.h
• ../virt-dma.h

Detected Declarations

• struct omap_dma_config
• struct omap_dma_context
• struct omap_dmadev
• struct omap_chan
• struct omap_type2_desc
• struct omap_sg
• struct omap_desc
• function omap_dma_desc_free
• function omap_dma_fill_type2_desc
• function omap_dma_write
• function omap_dma_read
• function omap_dma_glbl_write
• function omap_dma_glbl_read
• function omap_dma_chan_write
• function omap_dma_chan_read
• function omap_dma_clear_csr
• function omap_dma_get_csr
• function omap_dma_clear_lch
• function omap_dma_assign
• function omap_dma_start
• function omap_dma_drain_chan
• function omap_dma_stop
• function omap_dma_start_sg
• function omap_dma_start_desc
• function omap_dma_callback
• function omap_dma_irq
• function omap_dma_get_lch
• function omap_dma_put_lch
• function omap_dma_legacy
• function omap_dma_alloc_chan_resources
• function omap_dma_free_chan_resources
• function omap_dma_sg_size
• function omap_dma_desc_size
• function omap_dma_desc_size_pos
• function omap_dma_chan_read_3_3
• function omap_dma_get_src_pos
• function omap_dma_get_dst_pos
• function omap_dma_tx_status
• function omap_dma_issue_pending
• function for_each_sg
• function omap_dma_slave_config
• function omap_dma_terminate_all
• function omap_dma_stop
• function omap_dma_synchronize
• function omap_dma_pause
• function omap_dma_resume
• function omap_dma_chan_init
• function omap_dma_free

Annotated Snippet

subsys_initcall(omap_dma_init);

static void __exit omap_dma_exit(void)
{
	platform_driver_unregister(&omap_dma_driver);
}
module_exit(omap_dma_exit);

MODULE_AUTHOR("Russell King");
MODULE_DESCRIPTION("Texas Instruments sDMA DMAengine support");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/cpu_pm.h`, `linux/delay.h`, `linux/dmaengine.h`, `linux/dma-mapping.h`, `linux/dmapool.h`, `linux/err.h`, `linux/init.h`, `linux/interrupt.h`.
• Detected declarations: `struct omap_dma_config`, `struct omap_dma_context`, `struct omap_dmadev`, `struct omap_chan`, `struct omap_type2_desc`, `struct omap_sg`, `struct omap_desc`, `function omap_dma_desc_free`, `function omap_dma_fill_type2_desc`, `function omap_dma_write`.
• 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.