sound/aoa/codecs/tas-basstreble.h
Source file repositories/reference/linux-study-clean/sound/aoa/codecs/tas-basstreble.h
File Facts
- System
- Linux kernel
- Corpus path
sound/aoa/codecs/tas-basstreble.h- Extension
.h- Size
- 1453 bytes
- Lines
- 136
- Domain
- Driver Families
- Bucket
- sound/aoa
- 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.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
function tas3004_treblefunction tas3004_bass
Annotated Snippet
#define TAS3004_TREBLE_MIN 0
#define TAS3004_TREBLE_MAX 72
#define TAS3004_BASS_MIN 0
#define TAS3004_BASS_MAX 72
#define TAS3004_TREBLE_ZERO 36
#define TAS3004_BASS_ZERO 36
static const u8 tas3004_treble_table[] = {
150, /* -18 dB */
149,
148,
147,
146,
145,
144,
143,
142,
141,
140,
139,
138,
137,
136,
135,
134,
133,
132,
131,
130,
129,
128,
127,
126,
125,
124,
123,
122,
121,
120,
119,
118,
117,
116,
115,
114, /* 0 dB */
113,
112,
111,
109,
108,
107,
105,
104,
103,
101,
99,
98,
96,
93,
91,
89,
86,
83,
81,
77,
74,
71,
67,
63,
59,
54,
49,
44,
38,
32,
26,
19,
10,
4,
2,
1, /* +18 dB */
};
static inline u8 tas3004_treble(int idx)
{
return tas3004_treble_table[idx];
}
/* I only save the difference here to the treble table
* so that the binary is smaller...
Annotation
- Detected declarations: `function tas3004_treble`, `function tas3004_bass`.
- Atlas domain: Driver Families / sound/aoa.
- 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.