diff options
author | Richard Fitzgerald <rf@opensource.cirrus.com> | 2025-03-23 20:05:29 +0300 |
---|---|---|
committer | Mark Brown <broonie@kernel.org> | 2025-03-25 17:21:51 +0300 |
commit | 2593f7e0dc93a898a84220b3fb180d86f1ca8c60 (patch) | |
tree | efe80529c6880cccbf501b648e9e2cbc62d3f779 /lib/string_helpers.c | |
parent | 9ef52d529bb75071e03cf85078f724d69c4abe89 (diff) | |
download | linux-2593f7e0dc93a898a84220b3fb180d86f1ca8c60.tar.xz |
firmware: cs_dsp: Ensure cs_dsp_load[_coeff]() returns 0 on success
Set ret = 0 on successful completion of the processing loop in
cs_dsp_load() and cs_dsp_load_coeff() to ensure that the function
returns 0 on success.
All normal firmware files will have at least one data block, and
processing this block will set ret == 0, from the result of either
regmap_raw_write() or cs_dsp_parse_coeff().
The kunit tests create a dummy firmware file that contains only the
header, without any data blocks. This gives cs_dsp a file to "load"
that will not cause any side-effects. As there aren't any data blocks,
the processing loop will not set ret == 0.
Originally there was a line after the processing loop:
ret = regmap_async_complete(regmap);
which would set ret == 0 before the function returned.
Commit fe08b7d5085a ("firmware: cs_dsp: Remove async regmap writes")
changed the regmap write to a normal sync write, so the call to
regmap_async_complete() wasn't necessary and was removed. It was
overlooked that the ret here wasn't only to check the result of
regmap_async_complete(), it also set the final return value of the
function.
Fixes: fe08b7d5085a ("firmware: cs_dsp: Remove async regmap writes")
Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com>
Link: https://patch.msgid.link/20250323170529.197205-1-rf@opensource.cirrus.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'lib/string_helpers.c')
0 files changed, 0 insertions, 0 deletions