drivers/dma/stm32/stm32-mdma.c
Source file repositories/reference/linux-study-clean/drivers/dma/stm32/stm32-mdma.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/dma/stm32/stm32-mdma.c- Extension
.c- Size
- 53739 bytes
- Lines
- 1830
- 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.hlinux/clk.hlinux/delay.hlinux/dmaengine.hlinux/dma-mapping.hlinux/dmapool.hlinux/err.hlinux/init.hlinux/iopoll.hlinux/jiffies.hlinux/list.hlinux/log2.hlinux/module.hlinux/of.hlinux/of_dma.hlinux/platform_device.hlinux/pm_runtime.hlinux/reset.hlinux/slab.h../virt-dma.h
Detected Declarations
struct stm32_mdma_chan_configstruct stm32_mdma_hwdescstruct stm32_mdma_desc_nodestruct stm32_mdma_descstruct stm32_mdma_dma_configstruct stm32_mdma_chanstruct stm32_mdma_deviceenum stm32_mdma_trigger_modeenum stm32_mdma_widthenum stm32_mdma_inc_modefunction stm32_mdma_readfunction stm32_mdma_writefunction stm32_mdma_set_bitsfunction stm32_mdma_clr_bitsfunction stm32_mdma_desc_freefunction stm32_mdma_get_widthfunction stm32_mdma_get_max_widthfunction stm32_mdma_get_best_burstfunction stm32_mdma_disable_chanfunction stm32_mdma_stopfunction stm32_mdma_set_busfunction stm32_mdma_set_xfer_paramfunction stm32_mdma_dump_hwdescfunction stm32_mdma_setup_hwdescfunction stm32_mdma_setup_xferfunction for_each_sgfunction stm32_mdma_prep_slave_sgfunction stm32_mdma_prep_dma_cyclicfunction stm32_mdma_prep_dma_memcpyfunction stm32_mdma_dump_regfunction stm32_mdma_start_transferfunction stm32_mdma_issue_pendingfunction stm32_mdma_pausefunction stm32_mdma_resumefunction stm32_mdma_terminate_allfunction stm32_mdma_synchronizefunction stm32_mdma_slave_configfunction stm32_mdma_desc_residuefunction stm32_mdma_tx_statusfunction stm32_mdma_xfer_endfunction stm32_mdma_irq_handlerfunction stm32_mdma_alloc_chan_resourcesfunction stm32_mdma_free_chan_resourcesfunction stm32_mdma_filter_fnfunction stm32_mdma_probefunction stm32_mdma_runtime_suspendfunction stm32_mdma_runtime_resumefunction stm32_mdma_pm_suspend
Annotated Snippet
subsys_initcall(stm32_mdma_init);
MODULE_DESCRIPTION("Driver for STM32 MDMA controller");
MODULE_AUTHOR("M'boumba Cedric Madianga <cedric.madianga@gmail.com>");
MODULE_AUTHOR("Pierre-Yves Mordret <pierre-yves.mordret@st.com>");
Annotation
- Immediate include surface: `linux/bitfield.h`, `linux/clk.h`, `linux/delay.h`, `linux/dmaengine.h`, `linux/dma-mapping.h`, `linux/dmapool.h`, `linux/err.h`, `linux/init.h`.
- Detected declarations: `struct stm32_mdma_chan_config`, `struct stm32_mdma_hwdesc`, `struct stm32_mdma_desc_node`, `struct stm32_mdma_desc`, `struct stm32_mdma_dma_config`, `struct stm32_mdma_chan`, `struct stm32_mdma_device`, `enum stm32_mdma_trigger_mode`, `enum stm32_mdma_width`, `enum stm32_mdma_inc_mode`.
- 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.