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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 9 Jun 2022 08:20:53 +0000 (10:20 +0200)
commitd68a5eb7b3e03e5836c0f2fc42d6fa9150bf5db6
tree83e1334db8510150137e4b97a0e2a5196e6ddb8c
parent9b42659cb3c44caa605ee1a9f91147d7bff16bf1
ASoC: dapm: Don't fold register value changes into notifications

[ Upstream commit ad685980469b9f9b99d4d6ea05f4cb8f57cb2234 ]

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>
Signed-off-by: Sasha Levin <sashal@kernel.org>
sound/soc/soc-dapm.c