ASoC: ops: add correct range check for limiting volume
authorSrinivas Kandagatla <srinivas.kandagatla@linaro.org>
Mon, 4 Dec 2023 12:47:35 +0000 (12:47 +0000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 13 Dec 2023 17:45:31 +0000 (18:45 +0100)
commit fb9ad24485087e0f00d84bee7a5914640b2b9024 upstream.

Volume can have ranges that start with negative values, ex: -84dB to
+40dB. Apply correct range check in snd_soc_limit_volume before setting
the platform_max. Without this patch, for example setting a 0dB limit on
a volume range of -84dB to +40dB would fail.

Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Tested-by: Johan Hovold <johan+linaro@kernel.org>
Reviewed-by: Johan Hovold <johan+linaro@kernel.org>
Link: https://lore.kernel.org/r/20231204124736.132185-2-srinivas.kandagatla@linaro.org
Signed-off-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
sound/soc/soc-ops.c

index 55b009d..2d25748 100644 (file)
@@ -661,7 +661,7 @@ int snd_soc_limit_volume(struct snd_soc_card *card,
        kctl = snd_soc_card_get_kcontrol(card, name);
        if (kctl) {
                struct soc_mixer_control *mc = (struct soc_mixer_control *)kctl->private_value;
-               if (max <= mc->max) {
+               if (max <= mc->max - mc->min) {
                        mc->platform_max = max;
                        ret = 0;
                }