drivers/pci/controller/dwc/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/pci/controller/dwc/Kconfig

Extension

[no extension]

Size

18231 bytes

Lines

564

Domain

Representative Device Path

Bucket

PCIe NVMe Storage Path

Inferred role

Representative Device Path: build/configuration rule

Status

atlas-only

Why This File Exists

Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.

• Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.
• 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

menu "DesignWare-based PCIe controllers"
	depends on PCI

config PCIE_DW
	bool

config PCIE_DW_DEBUGFS
	bool "DesignWare PCIe debugfs entries"
	depends on DEBUG_FS
	depends on PCIE_DW_HOST || PCIE_DW_EP
	help
	  Say Y here to enable debugfs entries for the PCIe controller. These
	  entries provide various debug features related to the controller and
	  expose the RAS DES capabilities such as Silicon Debug, Error Injection
	  and Statistical Counters.

config PCIE_DW_HOST
	bool
	select PCIE_DW
	select IRQ_MSI_LIB
	select PCI_HOST_COMMON

config PCIE_DW_EP
	bool
	select PCIE_DW

config PCIE_AL
	bool "Amazon Annapurna Labs PCIe controller"
	depends on OF && (ARM64 || COMPILE_TEST)
	depends on PCI_MSI
	select PCIE_DW_HOST
	select PCI_ECAM
	help
	  Say Y here to enable support of the Amazon's Annapurna Labs PCIe
	  controller IP on Amazon SoCs. The PCIe controller uses the DesignWare
	  core plus Annapurna Labs proprietary hardware wrappers. This is
	  required only for DT-based platforms. ACPI platforms with the
	  Annapurna Labs PCIe controller don't need to enable this.

config PCIE_AMD_MDB
	bool "AMD MDB Versal2 PCIe controller"
	depends on OF && (ARM64 || COMPILE_TEST)
	depends on PCI_MSI
	select PCIE_DW_HOST
	help
	  Say Y here if you want to enable PCIe controller support on AMD
	  Versal2 SoCs. The AMD MDB Versal2 PCIe controller is based on
	  DesignWare IP and therefore the driver re-uses the DesignWare
	  core functions to implement the driver.

config PCI_MESON
	tristate "Amlogic Meson PCIe controller"
	default m if ARCH_MESON
	depends on PCI_MSI
	select PCIE_DW_HOST
	help
	  Say Y here if you want to enable PCI controller support on Amlogic
	  SoCs. The PCI controller on Amlogic is based on DesignWare hardware
	  and therefore the driver re-uses the DesignWare core functions to
	  implement the driver.

config PCIE_ANDES_QILAI
	tristate "Andes QiLai PCIe controller"
	depends on ARCH_ANDES || COMPILE_TEST
	depends on PCI_MSI
	select PCIE_DW_HOST
	help
	  Say Y here to enable PCIe controller support on Andes QiLai SoCs,

Annotation

• Atlas domain: Representative Device Path / PCIe NVMe Storage Path.
• 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.