drivers/dma/dw-edma/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/dma/dw-edma/Kconfig
Extension: [no extension]
Size: 593 bytes
Lines: 23
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.
Touches IRQ or DMA behavior; this matters for the representative real-device path.

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

config DW_EDMA
	tristate "Synopsys DesignWare eDMA controller driver"
	depends on PCI && PCI_MSI
	select DMA_ENGINE
	select DMA_VIRTUAL_CHANNELS
	help
	  Support the Synopsys DesignWare eDMA controller, normally
	  implemented on endpoints SoCs.

if DW_EDMA

config DW_EDMA_PCIE
	tristate "Synopsys DesignWare eDMA PCIe driver"
	depends on PCI && PCI_MSI
	help
	  Provides a glue-logic between the Synopsys DesignWare
	  eDMA controller and an endpoint PCIe device. This also serves
	  as a reference design to whom desires to use this IP.

endif # DW_EDMA

Annotation

Atlas domain: Driver Families / drivers/dma.
Implementation status: atlas-only.
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.