sound/soc/tegra/tegra30_i2s.h

File Facts

System

Linux kernel

Corpus path

sound/soc/tegra/tegra30_i2s.h

Extension

.h

Size

10990 bytes

Lines

241

Domain

Driver Families

Bucket

sound/soc

Inferred role

Driver Families: implementation source

Status

source implementation candidate

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• tegra_pcm.h

Detected Declarations

• struct tegra30_i2s_soc_data
• struct tegra30_i2s

Annotated Snippet

struct tegra30_i2s_soc_data {
	void (*set_audio_cif)(struct regmap *regmap,
			      unsigned int reg,
			      struct tegra30_ahub_cif_conf *conf);
};

struct tegra30_i2s {
	const struct tegra30_i2s_soc_data *soc_data;
	struct snd_soc_dai_driver dai;
	int cif_id;
	struct clk *clk_i2s;
	enum tegra30_ahub_txcif capture_i2s_cif;
	enum tegra30_ahub_rxcif capture_fifo_cif;
	char capture_dma_chan[8];
	struct snd_dmaengine_dai_dma_data capture_dma_data;
	enum tegra30_ahub_rxcif playback_i2s_cif;
	enum tegra30_ahub_txcif playback_fifo_cif;
	char playback_dma_chan[8];
	struct snd_dmaengine_dai_dma_data playback_dma_data;
	struct regmap *regmap;
	struct snd_dmaengine_pcm_config dma_config;
};

#endif

Annotation

• Immediate include surface: `tegra_pcm.h`.
• Detected declarations: `struct tegra30_i2s_soc_data`, `struct tegra30_i2s`.
• Atlas domain: Driver Families / sound/soc.
• Implementation status: source implementation candidate.

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.