mirror of
https://github.com/torvalds/linux.git
synced 2026-09-27 11:02:03 +02:00
ASoC: tas2562: fix DVC coefficient write order
The TAS2562 applies the 32-bit digital volume coefficient to the
playback path when the last byte, DVC_CFG4 (book 0 page 2 reg 0x0F), is
written. tas2562_volume_control_put() wrote DVC_CFG4 first and DVC_CFG1
(the MSB) last, so every volume change latched a value made of the
previous coefficient's upper three bytes combined with the new LSB; the
remaining bytes only took effect on the next volume change.
In practice the control was unusable: the first setting after power-on
always played at roughly 0 dB no matter what value was requested (the
chip's default upper bytes were still latched), and most subsequent
changes muted the output entirely or produced a distorted, over-unity
gain.
Verified on a TAS2562 (ADLINK OSM-520 / MT8189 board) by tracing the
I2C writes with ftrace and by writing the same coefficients manually in
both byte orders: written MSB-first the register block behaves exactly
as the driver expects, LSB-first reproduces the broken behaviour.
Write the bytes MSB first with DVC_CFG4 last so the complete new
coefficient is latched atomically.
Fixes: bf726b1c86 ("ASoC: tas2562: Add support for digital volume control")
Cc: stable@vger.kernel.org
Signed-off-by: Haidar Lee <haidar.lee@adlinktech.com>
Link: https://patch.msgid.link/20260715-tas2562-dvc-fix-v1-1-072b13901b20@adlinktech.com
Signed-off-by: Mark Brown <broonie@kernel.org>
This commit is contained in:
parent
1590cf0329
commit
8e957e4907
|
|
@ -475,20 +475,27 @@ static int tas2562_volume_control_put(struct snd_kcontrol *kcontrol,
|
|||
u32 reg_val;
|
||||
|
||||
reg_val = float_vol_db_lookup[ucontrol->value.integer.value[0]/2];
|
||||
ret = snd_soc_component_write(component, TAS2562_DVC_CFG4,
|
||||
(reg_val & 0xff));
|
||||
if (ret)
|
||||
return ret;
|
||||
ret = snd_soc_component_write(component, TAS2562_DVC_CFG3,
|
||||
((reg_val >> 8) & 0xff));
|
||||
/*
|
||||
* The device applies the 32-bit coefficient to the playback path on
|
||||
* the write to DVC_CFG4 (the LSB, book 0 page 2 reg 0x0F), so the
|
||||
* bytes must be written MSB first and DVC_CFG4 last. Writing CFG4
|
||||
* first latches a mix of the previous coefficient's upper bytes and
|
||||
* the new LSB instead of the requested value.
|
||||
*/
|
||||
ret = snd_soc_component_write(component, TAS2562_DVC_CFG1,
|
||||
((reg_val >> 24) & 0xff));
|
||||
if (ret)
|
||||
return ret;
|
||||
ret = snd_soc_component_write(component, TAS2562_DVC_CFG2,
|
||||
((reg_val >> 16) & 0xff));
|
||||
if (ret)
|
||||
return ret;
|
||||
ret = snd_soc_component_write(component, TAS2562_DVC_CFG1,
|
||||
((reg_val >> 24) & 0xff));
|
||||
ret = snd_soc_component_write(component, TAS2562_DVC_CFG3,
|
||||
((reg_val >> 8) & 0xff));
|
||||
if (ret)
|
||||
return ret;
|
||||
ret = snd_soc_component_write(component, TAS2562_DVC_CFG4,
|
||||
(reg_val & 0xff));
|
||||
if (ret)
|
||||
return ret;
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user