drivers/dma/dw/Kconfig

Source file repositories/reference/linux-study-clean/drivers/dma/dw/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/dma/dw/Kconfig
Extension: [no extension]
Size: 943 bytes
Lines: 37
Domain: Driver Families
Bucket: drivers/dma
Inferred role: Driver Families: build/configuration rule
Status: atlas-only

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.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0

#
# DMA engine configuration for dw
#

config DW_DMAC_CORE
	tristate
	select DMA_ENGINE

config DW_DMAC
	tristate "Synopsys DesignWare AHB DMA platform driver"
	depends on HAS_IOMEM
	select DW_DMAC_CORE
	help
	  Support the Synopsys DesignWare AHB DMA controller. This
	  can be integrated in chips such as the Intel Cherrytrail.

config RZN1_DMAMUX
	tristate "Renesas RZ/N1 DMAMUX driver"
	depends on DW_DMAC
	depends on ARCH_RZN1 || COMPILE_TEST
	help
	  Support the Renesas RZ/N1 DMAMUX which is located in front of
	  the Synopsys DesignWare AHB DMA controller located on Renesas
	  SoCs.

config DW_DMAC_PCI
	tristate "Synopsys DesignWare AHB DMA PCI driver"
	depends on PCI
	depends on HAS_IOMEM
	select DW_DMAC_CORE
	help
	  Support the Synopsys DesignWare AHB DMA controller on the
	  platforms that enumerate it as a PCI device. For example,
	  Intel Medfield has integrated this GPDMA controller.

Annotation

Atlas domain: Driver Families / drivers/dma.
Implementation status: atlas-only.

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.