]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
ASoC: Intel: avs: Fix return status of avs_pcm_hw_constraints_init()
authorAmadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
Thu, 10 Oct 2024 11:20:08 +0000 (13:20 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 14 Dec 2024 19:04:15 +0000 (20:04 +0100)
commitb050c6284a20bf7202ff1507ede925d0018c2d40
tree9ce4b514ec4a9928a4661f8363a1a3b876dd489c
parent871caea15202cc0ee9fcf0bd11b2e846a8bacdbc
ASoC: Intel: avs: Fix return status of avs_pcm_hw_constraints_init()

commit a0aae96be5ffc5b456ca07bfe1385b721c20e184 upstream.

Check for return code from avs_pcm_hw_constraints_init() in
avs_dai_fe_startup() only checks if value is different from 0. Currently
function can return positive value, change it to return 0 on success.

Reviewed-by: Cezary Rojewski <cezary.rojewski@intel.com>
Signed-off-by: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
I've observed KASAN on our setups and while patch itself is correct
regardless. Problem seems to be caused by recent changes to rates, as
this started happening after recent patchsets and doesn't reproduce with
those reverted
https://lore.kernel.org/linux-sound/20240905-alsa-12-24-128-v1-0-8371948d3921@baylibre.com/
https://lore.kernel.org/linux-sound/20240911135756.24434-1-tiwai@suse.de/
I've tested using Mark tree, where they are both applied and for some
reason snd_pcm_hw_constraint_minmax() started returning positive value,
while previously it returned 0. I'm bit worried if it signals some
potential deeper problem regarding constraints with above changes.

Link: https://patch.msgid.link/20241010112008.545526-1-amadeuszx.slawinski@linux.intel.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
sound/soc/intel/avs/pcm.c