drivers/dma/ti/edma.c

File Facts

System

Linux kernel

Corpus path

drivers/dma/ti/edma.c

Extension

.c

Size

71427 bytes

Lines

2703

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/dmaengine.h
• linux/dma-mapping.h
• linux/bitmap.h
• linux/err.h
• linux/init.h
• linux/interrupt.h
• linux/list.h
• linux/module.h
• linux/platform_device.h
• linux/slab.h
• linux/spinlock.h
• linux/string_choices.h
• linux/of.h
• linux/of_dma.h
• linux/of_irq.h
• linux/of_address.h
• linux/pm_runtime.h
• linux/platform_data/edma.h
• ../dmaengine.h
• ../virt-dma.h

Detected Declarations

• struct edmacc_param
• struct edma_pset
• struct edma_desc
• struct edma_cc
• struct edma_tc
• struct edma_chan
• struct edma_cc
• function edma_read
• function edma_write
• function edma_modify
• function edma_or
• function edma_read_array
• function edma_write_array
• function edma_modify_array
• function edma_or_array2
• function edma_write_array2
• function edma_shadow0_read_array
• function edma_shadow0_write
• function edma_shadow0_write_array
• function edma_param_modify
• function edma_assign_priority_to_queue
• function edma_set_chmap
• function edma_setup_interrupt
• function edma_write_slot
• function edma_read_slot
• function edma_alloc_slot
• function edma_free_slot
• function edma_link
• function edma_get_position
• function edma_start
• function edma_stop
• function edma_pause
• function edma_resume
• function edma_trigger_channel
• function edma_clean_channel
• function edma_assign_channel_eventq
• function edma_alloc_channel
• function edma_free_channel
• function edma_desc_free
• function edma_execute
• function edma_terminate_all
• function edma_dma
• function edma_synchronize
• function edma_slave_config
• function edma_dma_pause
• function edma_dma_resume
• function edma_config_pset
• function edma_prep_dma_interleaved

Annotated Snippet

subsys_initcall(edma_init);

static void __exit edma_exit(void)
{
	platform_driver_unregister(&edma_driver);
	platform_driver_unregister(&edma_tptc_driver);
}
module_exit(edma_exit);

MODULE_AUTHOR("Matt Porter <matt.porter@linaro.org>");
MODULE_DESCRIPTION("TI EDMA DMA engine driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/dmaengine.h`, `linux/dma-mapping.h`, `linux/bitmap.h`, `linux/err.h`, `linux/init.h`, `linux/interrupt.h`, `linux/list.h`, `linux/module.h`.
• Detected declarations: `struct edmacc_param`, `struct edma_pset`, `struct edma_desc`, `struct edma_cc`, `struct edma_tc`, `struct edma_chan`, `struct edma_cc`, `function edma_read`, `function edma_write`, `function edma_modify`.
• 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.