sound/soc/ux500/Kconfig

Source file repositories/reference/linux-study-clean/sound/soc/ux500/Kconfig

File Facts

System: Linux kernel
Corpus path: sound/soc/ux500/Kconfig
Extension: [no extension]
Size: 910 bytes
Lines: 34
Domain: Driver Families
Bucket: sound/soc
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
#
# Ux500 SoC audio configuration
#
menuconfig SND_SOC_UX500
	tristate "Ux500"
	depends on SND_SOC
	depends on MFD_DB8500_PRCMU
	help
		Say Y if you want to enable ASoC-support for
		any of the Ux500 platforms (e.g. U8500).

config SND_SOC_UX500_PLAT_MSP_I2S
	tristate
	depends on SND_SOC_UX500

config SND_SOC_UX500_PLAT_DMA
	tristate "Platform - DB8500 (DMA)"
	depends on SND_SOC_UX500
	select SND_SOC_GENERIC_DMAENGINE_PCM
	help
		Say Y if you want to enable the Ux500 platform-driver.

config SND_SOC_UX500_MACH_MOP500
	tristate "Machine - MOP500 (Ux500 + AB8500)"
	depends on AB8500_CORE && AB8500_GPADC && SND_SOC_UX500
	select SND_SOC_AB8500_CODEC
	select SND_SOC_UX500_PLAT_MSP_I2S
	select SND_SOC_UX500_PLAT_DMA
	help
		Select this to enable the MOP500 machine-driver.
		This will enable platform-drivers for: Ux500
		This will enable codec-drivers for: AB8500

Annotation

Atlas domain: Driver Families / sound/soc.
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.