ASoC: dapm: Don't fold register value changes into notifications
DAPM tracks and reports the value presented to the user from DAPM controls separately to the register value, these may diverge during initialisation or when an autodisable control is in use. When writing DAPM controls we currently report that a change has occurred if either the DAPM value or the value stored in the register has changed, meaning that if the two are out of sync we may appear to report a spurious event to userspace. Since we use this folded in value for nothing other than the value reported to userspace simply drop the folding in of the register change. Signed-off-by: Mark Brown <broonie@kernel.org> Link: https://lore.kernel.org/r/20220428161833.3690050-1-broonie@kernel.org Signed-off-by: Mark Brown <broonie@kernel.org>
This commit is contained in:
parent
a0746cbd0b
commit
ad68598046
|
@ -3437,7 +3437,6 @@ int snd_soc_dapm_put_volsw(struct snd_kcontrol *kcontrol,
|
|||
update.val = val;
|
||||
card->update = &update;
|
||||
}
|
||||
change |= reg_change;
|
||||
|
||||
ret = soc_dapm_mixer_update_power(card, kcontrol, connect,
|
||||
rconnect);
|
||||
|
@ -3539,7 +3538,6 @@ int snd_soc_dapm_put_enum_double(struct snd_kcontrol *kcontrol,
|
|||
update.val = val;
|
||||
card->update = &update;
|
||||
}
|
||||
change |= reg_change;
|
||||
|
||||
ret = soc_dapm_mux_update_power(card, kcontrol, item[0], e);
|
||||
|
||||
|
|
Loading…
Reference in New Issue