Re: [PATCH] ASoC: es9356: fix the capture gain dB scale

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] ASoC: es9356: missing Fixes trailer for commit 5d9cb740cd38
--

commit 52267100487603f3acb6a660175cdbfe55292773
Author: Zachary Huang <zuzhenhuang365@gmail.com>

> ASoC: es9356: fix the capture gain dB scale
>
> The two capture gain controls are declared with a TLV step of 3 (FU33,
> analog mic) and 6 (FU11, DMIC).  The TLV step is expressed in 0.01 dB
> units, so this advertises 0.03 dB and 0.06 dB per step: with a value
> range of 0..10 and 0..3 the whole controls appear to span only 0.30 dB
> and 0.18 dB.
>
> The hardware steps are 3 dB and 6 dB, i.e. 0..30 dB and 0..18 dB.
> Measured on a MECHREVO WUJIE 14SAH (ES9356 on SoundWire link 0) by
> recording the same signal at all four FU11 settings:
>
>     FU11=0   rms  523  (-35.9 dBFS)
>     FU11=1   rms 1007  (-30.3 dBFS)
>     FU11=2   rms 2011  (-24.2 dBFS)
>     FU11=3   rms 3794  (-18.7 dBFS)
>
> That is about +6 dB per step, matching the hardware definition rather
> than the advertised 0.06 dB.
>
> Because userspace (alsamixer, PipeWire/WirePlumber) derives the volume
> from this TLV, the capture gain currently looks like a control without
> any usable range, which is also why the default setting seems impossible
> to raise from the desktop.
>
> Assisted-by: LLM
> Signed-off-by: Zachary Huang <zuzhenhuang365@gmail.com>

[Severity: Low]
Should this bug fix include a Fixes: tag for the commit that introduced
the driver with the wrong TLV step units:

  Fixes: 5d9cb740cd38 ("ASoC: es9356-sdca: Add ES9356 SDCA driver")

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/179398005797.39773.18432202435074682955@gmail.com?part=1