]> www.infradead.org Git - users/jedix/linux-maple.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)
committerMark Brown <broonie@kernel.org>
Thu, 10 Oct 2024 16:03:07 +0000 (17:03 +0100)
commita0aae96be5ffc5b456ca07bfe1385b721c20e184
treec8c200046e51b5973a1d92cc2149a13a55d50193
parent8658c4eb9d6b76311322c1b74b3d4e0dec3599d8
ASoC: Intel: avs: Fix return status of avs_pcm_hw_constraints_init()

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>
sound/soc/intel/avs/pcm.c