sound/sh/Kconfig
Source file repositories/reference/linux-study-clean/sound/sh/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
sound/sh/Kconfig- Extension
[no extension]- Size
- 721 bytes
- Lines
- 33
- Domain
- Driver Families
- Bucket
- sound/sh
- 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 SH drivers
menuconfig SND_SUPERH
bool "SUPERH sound devices"
depends on SUPERH
default y
help
Support for sound devices specific to SUPERH architectures.
Drivers that are implemented on ASoC can be found in
"ALSA for SoC audio support" section.
if SND_SUPERH
config SND_AICA
tristate "Dreamcast Yamaha AICA sound"
depends on SH_DREAMCAST && SH_DMA_API
select SND_PCM
select G2_DMA
help
ALSA Sound driver for the SEGA Dreamcast console.
config SND_SH_DAC_AUDIO
tristate "SuperH DAC audio support"
depends on SND
depends on CPU_SH3 && HIGH_RES_TIMERS
select SND_PCM
help
Say Y here to include support for the on-chip DAC.
endif # SND_SUPERH
Annotation
- Atlas domain: Driver Families / sound/sh.
- 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.