sound/sparc/Kconfig

File Facts

System

Linux kernel

Corpus path

sound/sparc/Kconfig

Extension

[no extension]

Size

992 bytes

Lines

44

Domain

Driver Families

Bucket

sound/sparc

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
# ALSA Sparc drivers

menuconfig SND_SPARC
	bool "Sparc sound devices"
	depends on SPARC
	default y
	help
	  Support for sound devices specific to Sun SPARC architectures.

if SND_SPARC

config SND_SUN_AMD7930
	tristate "Sun AMD7930"
	depends on SBUS
	select SND_PCM
	help
	  Say Y here to include support for AMD7930 sound device on Sun.

	  To compile this driver as a module, choose M here: the module
	  will be called snd-sun-amd7930.

config SND_SUN_CS4231
	tristate "Sun CS4231"
	select SND_PCM
	select SND_TIMER
	help
	  Say Y here to include support for CS4231 sound device on Sun.

	  To compile this driver as a module, choose M here: the module
	  will be called snd-sun-cs4231.

config SND_SUN_DBRI
	tristate "Sun DBRI"
	depends on SBUS
	select SND_PCM
	help
	  Say Y here to include support for DBRI sound device on Sun.

	  To compile this driver as a module, choose M here: the module
	  will be called snd-sun-dbri.

endif	# SND_SPARC

Annotation

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