From 7cae68821c1c030fb8ae1659b81aa3ca0c61676d Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Thu, 29 Oct 2026 11:22:14 -0647 Subject: [PATCH] device/tegu NOTES: the TAS2572 RCA profile is linux-firmware's, not the factory image's The 10-26 audio entry said the amplifiers' tas2572RCA1.bin was the Pixel 9a's own file from the factory image. It is linux-firmware's ti/audio/tas257x/tas2572-1-1amp-reg.bin byte for byte (the sha the 10-26 run script pinned), and the factory image has no RCA-format profile. Found while writing the 9a's firmware list for tools/extract-vendor-firmware (#158). --- device/tegu/NOTES.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/device/tegu/NOTES.md b/device/tegu/NOTES.md index 31ad87f8e..14d362e25 100644 --- a/device/tegu/NOTES.md +++ b/device/tegu/NOTES.md @@ -19,9 +19,10 @@ Kernel `7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty`: the private integration tree for now (the pieces go to linux-omarchy-mobile one by one; the S2MPG14 RTC is #54), with the AoC started by a staged script. The card is `google,tegu-aoc-snd-card`; the TAS2572 amplifiers (I2C 19, top 0x48 and -bottom 0x49) take their gains from the owner's `tas2572RCA1.bin` (the Pixel -9a's own file from the factory image, not linux-firmware) at every playback -start, and the codec exposes only `Top/Bottom Speaker Digital Volume` = 220 +bottom 0x49) take their gains from `tas2572RCA1.bin` at every playback +start (corrected 10-29: that file is linux-firmware's +`ti/audio/tas257x/tas2572-1-1amp-reg.bin`, byte for byte; stock's factory +image carries no RCA-format profile, only its own `ti_sp_tuning.bin`), and the codec exposes only `Top/Bottom Speaker Digital Volume` = 220 (0 dB; 232 is +6 dB), unchanged during a 1 kHz tone at 100 % PipeWire volume. Without stock's speaker processing or protection in the path, PipeWire's 100 % is full scale into stock's amplifier gains, so the WirePlumber rule caps