DMAengine subsystem and SoC DMA controller drivers
DMA controllers are hardware blocks that shuffle data between memory and peripherals without tying up the CPU. This directory holds the shared DMAengine framework plus drivers for the DMA engines built into modern SoCs from Arm, Apple, AMD, Qualcomm, ST, TI, Xilinx and others, used in phones, laptops, embedded boards and servers.
It should stay because this is a live, heavily maintained subsystem covering DMA controllers from virtually every active SoC vendor — Arm, Apple, AMD, Qualcomm, STMicroelectronics, TI, Xilinx and many more. Core fixes were still landing in 2026, and hardware like Arm's CoreLink DMA-350 is actively being sold into new designs in 2025.
repository signals
243files
162,171source lines
1,408commits, 5y
+37,631 / −19,455lines added / removed, 5y
338authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 1,408 total · active in 60/61 months
Core dmaengine code also saw another 2026 fix series ('Fix refcount leak in channel register error path'), indicating ongoing upstream maintenance rather than removal.
A currently marketed hardware family represented in this directory exists in 2025-era products: Arm CoreLink DMA-350 is an actively promoted DMA controller IP block.
codex reasoning notes (technical)
`drivers/dma` is an umbrella subsystem directory, not a single obsolete chip driver: local shell inspection of Kconfig/Makefile shows many active vendor families (Arm DMA-350, Apple ADMAC, AMD, Qualcomm, STM32, TI, Xilinx, etc.). The two lore URLs were obtained via `lore_file_timeline` on `drivers/dma/dmaengine.c`, which showed sustained 2024-2026 patch activity and no removal signal. The kernel-doc URL was obtained by `web.search_query` on kernel.org, and the Arm DMA-350 URL by `web.search_query` on arm.com. Because this directory covers currently shipping SoC DMA IP and has no single successor driver, the correct recommendation is to keep it.