ASoC: dapm: Don't fold register value changes into notifications
authorMark Brown <broonie@kernel.org>
Thu, 28 Apr 2022 16:18:32 +0000 (17:18 +0100)
committerMark Brown <broonie@kernel.org>
Tue, 3 May 2022 12:42:26 +0000 (13:42 +0100)
commitad685980469b9f9b99d4d6ea05f4cb8f57cb2234
tree80c0435e7b8bc7657dc592f6866e5e3211f19675
parenta0746cbd0b8224c4c0e4ae59968075cb7c14762a
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>
sound/soc/soc-dapm.c