sound/soc/tegra/tegra210_adx.h
Source file repositories/reference/linux-study-clean/sound/soc/tegra/tegra210_adx.h
File Facts
- System
- Linux kernel
- Corpus path
sound/soc/tegra/tegra210_adx.h- Extension
.h- Size
- 3311 bytes
- Lines
- 100
- 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
linux/types.h
Detected Declarations
struct tegra210_adx_soc_datastruct tegra210_adx
Annotated Snippet
struct tegra210_adx_soc_data {
const struct regmap_config *regmap_conf;
const struct snd_kcontrol_new *controls;
unsigned int num_controls;
unsigned int max_ch;
unsigned int ram_depth;
unsigned int byte_mask_size;
unsigned int cya_offset;
};
struct tegra210_adx {
struct regmap *regmap;
unsigned int *byte_mask;
u16 *map;
const struct tegra210_adx_soc_data *soc_data;
};
#endif
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct tegra210_adx_soc_data`, `struct tegra210_adx`.
- 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.