drivers/pinctrl/pxa/Kconfig

Source file repositories/reference/linux-study-clean/drivers/pinctrl/pxa/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/pinctrl/pxa/Kconfig
Extension: [no extension]
Size: 616 bytes
Lines: 27
Domain: Driver Families
Bucket: drivers/pinctrl
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-only
if (ARCH_PXA || COMPILE_TEST)

config PINCTRL_PXA
	bool
	select PINMUX
	select PINCONF
	select GENERIC_PINCONF

config PINCTRL_PXA25X
	tristate "Marvell PXA25x pin controller driver"
	select PINCTRL_PXA
	default y if PXA25x
	help
	  This is the pinctrl, pinmux, pinconf driver for the Marvell
	  PXA2xx block found in the pxa25x platforms.

config PINCTRL_PXA27X
	tristate "Marvell PXA27x pin controller driver"
	select PINCTRL_PXA
	default y if PXA27x
	help
	  This is the pinctrl, pinmux, pinconf driver for the Marvell
	  PXA2xx block found in the pxa27x platforms.

endif

Annotation

Atlas domain: Driver Families / drivers/pinctrl.
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.