diff options
| author | Cristian Ciocaltea <cristian.ciocaltea@collabora.com> | 2023-08-24 22:38:37 +0300 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2023-08-24 21:10:45 +0100 |
| commit | 199cd64140f222c66b68ebe288a3fcd0570e2e41 (patch) | |
| tree | b677ffa2c1f7d92f7afcf00e77063727b9347ef7 /tools | |
| parent | 8886e1b03669c498f7a24bc5e483f46db5e81f82 (diff) | |
ASoC: soc-core.c: Do not error if a DAI link component is not found
A recent cleanup of soc_dai_link_sanity_check() is responsible for
generating lots of confusing errors before returning -EPROBE_DEFER:
acp5x_mach acp5x_mach.0: ASoC: Component acp5x_i2s_dma.0 not found for link acp5x-8821-play
[...]
acp5x_mach acp5x_mach.0: ASoC: Component spi-VLV1776:00 not found for link acp5x-CS35L41-Stereo
[...]
acp5x_mach acp5x_mach.0: ASoC: Component spi-VLV1776:01 not found for link acp5x-CS35L41-Stereo
Switch back to the initial behaviour of logging those messages on
KERN_DEBUG level instead of KERN_ERR.
While at it, use the correct form of the verb in 'component_not_find'
label.
Fixes: 0e66a2c69409 ("ASoC: soc-core.c: cleanup soc_dai_link_sanity_check()")
Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com
Link: https://lore.kernel.org/r/20230824193837.369761-1-cristian.ciocaltea@collabora.com
Signed-off-by: Mark Brown <broonie@kernel.org
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions