drivers/pci/controller/plda/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/pci/controller/plda/Kconfig

Extension

[no extension]

Size

805 bytes

Lines

32

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 "PLDA-based PCIe controllers"
	depends on PCI

config PCIE_PLDA_HOST
	bool
	select IRQ_MSI_LIB

config PCIE_MICROCHIP_HOST
	tristate "Microchip AXI PCIe controller"
	depends on PCI_MSI && OF
	select PCI_HOST_COMMON
	select PCIE_PLDA_HOST
	help
	  Say Y here if you want kernel to support the Microchip AXI PCIe
	  Host Bridge driver.

config PCIE_STARFIVE_HOST
	tristate "StarFive PCIe host controller"
	depends on PCI_MSI && OF
	depends on ARCH_STARFIVE || COMPILE_TEST
	select PCIE_PLDA_HOST
	help
	  Say Y here if you want to support the StarFive PCIe controller in
	  host mode. StarFive PCIe controller uses PLDA PCIe core.

	  If you choose to build this driver as module it will be dynamically
	  linked and module will be called pcie-starfive.ko.

endmenu

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.