drivers/pinctrl/cirrus/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/pinctrl/cirrus/Kconfig

Extension

[no extension]

Size

983 bytes

Lines

45

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
config PINCTRL_CS42L43
	tristate "Cirrus Logic CS42L43 Pinctrl Driver"
	depends on MFD_CS42L43
	select GPIOLIB
	select PINMUX
	select PINCONF
	select GENERIC_PINCONF
	help
	  Select this to support the GPIO/Pinctrl functions of the Cirrus
	  Logic CS42L43 PC CODEC.

config PINCTRL_LOCHNAGAR
	tristate "Cirrus Logic Lochnagar pinctrl driver"
	# Avoid clash caused by MIPS defining RST, which is used in the driver
	depends on MFD_LOCHNAGAR && !MIPS
	select GPIOLIB
	select PINMUX
	select PINCONF
	select GENERIC_PINCONF
	help
	  This driver supports configuring the GPIO and other pin configuration
	  of the Cirrus Logic Lochnagar audio development board.

# This is all selected by the Madera MFD driver Kconfig options
config PINCTRL_MADERA
	tristate
	select PINMUX
	select GENERIC_PINCONF

config PINCTRL_CS47L15
	bool

config PINCTRL_CS47L35
	bool

config PINCTRL_CS47L85
	bool

config PINCTRL_CS47L90
	bool

config PINCTRL_CS47L92
	bool

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.