diff options
author | Amadeusz Sławiński <[email protected]> | 2024-10-10 13:20:08 +0200 |
---|---|---|
committer | Mark Brown <[email protected]> | 2024-10-10 17:03:07 +0100 |
commit | a0aae96be5ffc5b456ca07bfe1385b721c20e184 (patch) | |
tree | c8c200046e51b5973a1d92cc2149a13a55d50193 /tools/perf/scripts/python/flamegraph.py | |
parent | 8658c4eb9d6b76311322c1b74b3d4e0dec3599d8 (diff) |
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 <[email protected]>
Signed-off-by: Amadeusz Sławiński <[email protected]>
--
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/[email protected]/
https://lore.kernel.org/linux-sound/[email protected]/
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/[email protected]
Signed-off-by: Mark Brown <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions