sound/spi/Kconfig
Source file repositories/reference/linux-study-clean/sound/spi/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
sound/spi/Kconfig- Extension
[no extension]- Size
- 950 bytes
- Lines
- 40
- Domain
- Driver Families
- Bucket
- sound/spi
- 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
#SPI drivers
menuconfig SND_SPI
bool "SPI sound devices"
depends on SPI
default y
help
Support for sound devices connected via the SPI bus.
if SND_SPI
config SND_AT73C213
tristate "Atmel AT73C213 DAC driver"
depends on ATMEL_SSC
select SND_PCM
help
Say Y here if you want to use the Atmel AT73C213 external DAC. This
DAC can be found on Atmel development boards.
This driver requires the Atmel SSC driver for sound sink, a
peripheral found on most AT91 microprocessors.
To compile this driver as a module, choose M here: the module will be
called snd-at73c213.
config SND_AT73C213_TARGET_BITRATE
int "Target bitrate for AT73C213"
depends on SND_AT73C213
default "48000"
range 8000 50000
help
Sets the target bitrate for the bitrate calculator in the driver.
Limited by hardware to be between 8000 Hz and 50000 Hz.
Set to 48000 Hz by default.
endif # SND_SPI
Annotation
- Atlas domain: Driver Families / sound/spi.
- 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.