Skip to content

vc4_hdmi: Avoid log spam for audio start failure #5265

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 6, 2022

Conversation

popcornmix
Copy link
Collaborator

We regularly get dmesg error reports of:
[ 18.184066] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[ 18.184098] MAI: soc_pcm_open() failed (-19)

Currently I get 30 of these when booting to desktop. We always say, ignore they are harmless, but removing them would be good.

A bit of investigation shows, for me, the errors are all generated by second, unused hdmi interface.

It shows as an alsa device, and pulseaudio attempts to open it (numerous times), generating a kernel error message each time.

systemctl --user restart pulseaudio.service generates 6 additional error messages.

The error messages all come through:

switch (ret) {

which suggests returning ENOTSUPP, rather that ENODEV will be quiet. And indeed it is.

Note: earlier kernels do not have the quiet ENOTSUPP, so additional cherry-picks will be needed to backport
Signed-off-by: Dom Cobley [email protected]

We regularly get dmesg error reports of:
[   18.184066] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
[   18.184098]  MAI: soc_pcm_open() failed (-19)

Currently I get 30 of these when booting to desktop.
We always say, ignore they are harmless, but removing them would be good.

A bit of investigation shows, for me, the errors are all generated by second, unused hdmi interface.

It shows as an alsa device, and pulseaudio attempts to open it (numerous times), generating a kernel
error message each time.

systemctl --user restart pulseaudio.service generates 6 additional error messages.

The error messages all come through:
https://github.com/raspberrypi/linux/blob/a009a9c0d79dfec114ee5102ec3d3325a172c952/sound/soc/soc-pcm.c#L39

which suggests returning ENOTSUPP, rather that ENODEV will be quiet. And indeed it is.

Note: earlier kernels do not have the quiet ENOTSUPP, so additional cherry-picks will be needed to backport
Signed-off-by: Dom Cobley <[email protected]>
@popcornmix
Copy link
Collaborator Author

See: #4575

@6by9
Copy link
Contributor

6by9 commented Dec 6, 2022

Looks reasonable to me.

@pelwell pelwell merged commit 70a5069 into raspberrypi:rpi-6.1.y Dec 6, 2022
@popcornmix popcornmix deleted the snd_soc_dai_startup branch December 6, 2022 16:23
@popcornmix
Copy link
Collaborator Author

I've also cherry-picked:
b63605b

to rpi-5.15.y and rpi-6.0.y trees which is needed to make ENOTSUPP quiet.
(it was a clean cherry-pick on 6.0, but needed minor fixing up in 5.15).

@popcornmix popcornmix restored the snd_soc_dai_startup branch December 6, 2022 16:42
popcornmix added a commit to raspberrypi/firmware that referenced this pull request Dec 6, 2022
popcornmix added a commit to raspberrypi/rpi-firmware that referenced this pull request Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants