sound/soc/xilinx/Kconfig

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

File Facts

System: Linux kernel
Corpus path: sound/soc/xilinx/Kconfig
Extension: [no extension]
Size: 889 bytes
Lines: 28
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
menu "Xilinx"

config SND_SOC_XILINX_I2S
	tristate "Audio support for the Xilinx I2S"
	help
	  Select this option to enable Xilinx I2S Audio. This enables
	  I2S playback and capture using xilinx soft IP. In transmitter
	  mode, IP receives audio in AES format, extracts PCM and sends
	  PCM data. In receiver mode, IP receives PCM audio and
	  encapsulates PCM in AES format and sends AES data.

config SND_SOC_XILINX_AUDIO_FORMATTER
	tristate "Audio support for the Xilinx audio formatter"
	help
	  Select this option to enable Xilinx audio formatter
	  support. This provides DMA platform device support for
	  audio functionality.

config SND_SOC_XILINX_SPDIF
	tristate "Audio support for the Xilinx SPDIF"
	help
	  Select this option to enable Xilinx SPDIF Audio.
	  This provides playback and capture of SPDIF audio in
	  AES format.

endmenu

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.