drivers/dma/stm32/stm32-dma.c

File Facts

System

Linux kernel

Corpus path

drivers/dma/stm32/stm32-dma.c

Extension

.c

Size

51799 bytes

Lines

1783

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/bitfield.h
• linux/clk.h
• linux/delay.h
• linux/dmaengine.h
• linux/dma-mapping.h
• linux/err.h
• linux/init.h
• linux/iopoll.h
• linux/jiffies.h
• linux/list.h
• linux/module.h
• linux/of.h
• linux/of_dma.h
• linux/platform_device.h
• linux/pm_runtime.h
• linux/reset.h
• linux/sched.h
• linux/slab.h
• ../virt-dma.h

Detected Declarations

• struct stm32_dma_cfg
• struct stm32_dma_chan_reg
• struct stm32_dma_sg_req
• struct stm32_dma_desc
• struct stm32_dma_mdma_config
• struct stm32_dma_chan
• struct stm32_dma_device
• enum stm32_dma_width
• enum stm32_dma_burst_size
• function stm32_dma_read
• function stm32_dma_write
• function stm32_dma_get_width
• function stm32_dma_get_max_width
• function stm32_dma_fifo_threshold_is_allowed
• function stm32_dma_is_burst_possible
• function stm32_dma_get_best_burst
• function stm32_dma_get_burst
• function stm32_dma_set_fifo_config
• function stm32_dma_slave_config
• function stm32_dma_irq_status
• function stm32_dma_irq_clear
• function stm32_dma_disable_chan
• function stm32_dma_stop
• function stm32_dma_terminate_all
• function stm32_dma_synchronize
• function stm32_dma_dump_reg
• function stm32_dma_sg_inc
• function stm32_dma_start_transfer
• function stm32_dma_configure_next_sg
• function stm32_dma_handle_chan_paused
• function wrong
• function stm32_dma_post_resume_reconfigure
• function stm32_dma_handle_chan_done
• function stm32_dma_chan_irq
• function stm32_dma_issue_pending
• function stm32_dma_pause
• function stm32_dma_resume
• function stm32_dma_set_xfer_param
• function stm32_dma_clear_reg
• function for_each_sg
• function stm32_dma_get_remaining_bytes
• function stm32_dma_is_current_sg
• function stm32_dma_desc_residue
• function stm32_dma_tx_status
• function stm32_dma_alloc_chan_resources
• function stm32_dma_free_chan_resources
• function stm32_dma_desc_free
• function stm32_dma_set_config

Annotated Snippet

subsys_initcall(stm32_dma_init);

Annotation

• Immediate include surface: `linux/bitfield.h`, `linux/clk.h`, `linux/delay.h`, `linux/dmaengine.h`, `linux/dma-mapping.h`, `linux/err.h`, `linux/init.h`, `linux/iopoll.h`.
• Detected declarations: `struct stm32_dma_cfg`, `struct stm32_dma_chan_reg`, `struct stm32_dma_sg_req`, `struct stm32_dma_desc`, `struct stm32_dma_mdma_config`, `struct stm32_dma_chan`, `struct stm32_dma_device`, `enum stm32_dma_width`, `enum stm32_dma_burst_size`, `function stm32_dma_read`.
• 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.