drivers/dma/ste_dma40.c

File Facts

System

Linux kernel

Corpus path

drivers/dma/ste_dma40.c

Extension

.c

Size

97562 bytes

Lines

3680

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/dma-mapping.h
• linux/kernel.h
• linux/slab.h
• linux/export.h
• linux/dmaengine.h
• linux/platform_device.h
• linux/clk.h
• linux/delay.h
• linux/log2.h
• linux/pm.h
• linux/pm_runtime.h
• linux/err.h
• linux/of.h
• linux/of_address.h
• linux/of_dma.h
• linux/amba/bus.h
• linux/regulator/consumer.h
• dmaengine.h
• ste_dma40.h
• ste_dma40_ll.h

Detected Declarations

• struct stedma40_platform_data
• struct d40_interrupt_lookup
• struct d40_reg_val
• struct d40_lli_pool
• struct d40_desc
• struct d40_lcla_pool
• struct d40_phy_res
• struct d40_base
• struct d40_chan
• struct d40_gen_dmac
• struct d40_base
• enum d40_command
• enum d40_events
• function chan_is_physical
• function chan_is_logical
• function d40_pool_lli_alloc
• function d40_pool_lli_free
• function d40_lcla_alloc_one
• function d40_lcla_free_all
• function d40_desc_remove
• function list_for_each_entry_safe
• function d40_desc_free
• function d40_desc_submit
• function d40_phy_lli_load
• function d40_desc_done
• function d40_log_lli_to_lcxa
• function d40_desc_load
• function d40_desc_queue
• function d40_psize_2_burst_size
• function d40_size_2_dmalen
• function d40_sg_2_dmalen
• function for_each_sg
• function __d40_execute_command_phy
• function d40_term_all
• function list_for_each_entry_safe
• function list_for_each_entry_safe
• function __d40_config_set_event
• function d40_config_set_event
• function d40_chan_has_events
• function __d40_execute_command_log
• function d40_channel_execute_command
• function d40_get_prmo
• function d40_config_write
• function d40_residue
• function d40_tx_is_linked
• function d40_pause
• function d40_resume
• function d40_tx_submit

Annotated Snippet

subsys_initcall(stedma40_init);

Annotation

• Immediate include surface: `linux/dma-mapping.h`, `linux/kernel.h`, `linux/slab.h`, `linux/export.h`, `linux/dmaengine.h`, `linux/platform_device.h`, `linux/clk.h`, `linux/delay.h`.
• Detected declarations: `struct stedma40_platform_data`, `struct d40_interrupt_lookup`, `struct d40_reg_val`, `struct d40_lli_pool`, `struct d40_desc`, `struct d40_lcla_pool`, `struct d40_phy_res`, `struct d40_base`, `struct d40_chan`, `struct d40_gen_dmac`.
• 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.