arch/powerpc/sysdev/Kconfig

Source file repositories/reference/linux-study-clean/arch/powerpc/sysdev/Kconfig

File Facts

System: Linux kernel
Corpus path: arch/powerpc/sysdev/Kconfig
Extension: [no extension]
Size: 609 bytes
Lines: 32
Domain: Architecture Layer
Bucket: arch/powerpc
Inferred role: Architecture Layer: build/configuration rule
Status: atlas-only

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
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
# For a description of the syntax of this configuration file,
# see Documentation/kbuild/kconfig-language.rst.
#

config PPC4xx_PCI_EXPRESS
	bool
	depends on PCI && 44x

config PPC4xx_HSTA_MSI
	bool
	depends on PCI_MSI
	depends on PCI && 44x

config PPC_MSI_BITMAP
	bool
	depends on PCI_MSI
	default y if MPIC
	default y if FSL_PCI
	default y if PPC_POWERNV

source "arch/powerpc/sysdev/xics/Kconfig"
source "arch/powerpc/sysdev/xive/Kconfig"

config GE_FPGA
	bool

config FSL_CORENET_RCPM
	bool
	help
	  This option enables support for RCPM (Run Control/Power Management).

Annotation

Atlas domain: Architecture Layer / arch/powerpc.
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.