vc4: hdmi: audio: ASoC: error at snd_soc_dai_startup on fef00700.hdmi
Hi,
yesterday i was testing with Linux 5.13-rc3 on my Raspberry Pi 4 B (multi_v7_defconfig) and i'm getting the following errors during boot:
[ 25.947494] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 25.947512] MAI: soc_pcm_open() failed (-19) [ 25.947883] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 25.947891] MAI: soc_pcm_open() failed (-19) [ 25.948566] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 25.948577] MAI: soc_pcm_open() failed (-19) [ 26.500049] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 26.500065] MAI: soc_pcm_open() failed (-19) [ 26.500608] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 26.500617] MAI: soc_pcm_open() failed (-19) [ 26.502339] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 26.502353] MAI: soc_pcm_open() failed (-19) [ 26.502569] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 26.502578] MAI: soc_pcm_open() failed (-19)
Rootfs: Raspberry Pi OS 32 bit (April 2021)
But according to aplay -l both hdmi devices have been registered. Does anyone have seen this, too?
Best regards Stefan
Hi Stefan,
On Wed, May 26, 2021 at 12:47:29PM +0200, Stefan Wahren wrote:
Hi,
yesterday i was testing with Linux 5.13-rc3 on my Raspberry Pi 4 B (multi_v7_defconfig) and i'm getting the following errors during boot:
[ 25.947494] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 25.947512] MAI: soc_pcm_open() failed (-19) [ 25.947883] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 25.947891] MAI: soc_pcm_open() failed (-19) [ 25.948566] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 25.948577] MAI: soc_pcm_open() failed (-19) [ 26.500049] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 26.500065] MAI: soc_pcm_open() failed (-19) [ 26.500608] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 26.500617] MAI: soc_pcm_open() failed (-19) [ 26.502339] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 26.502353] MAI: soc_pcm_open() failed (-19) [ 26.502569] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 26.502578] MAI: soc_pcm_open() failed (-19)
Rootfs: Raspberry Pi OS 32 bit (April 2021)
But according to aplay -l both hdmi devices have been registered. Does anyone have seen this, too?
I would assume it's due to this: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/driv...
It pre-dates my time working on the vc4 driver so I'm not really sure what this is supposed to prevent, but my guess is that it's there to avoid someone using the audio card before we have a display detected and connected, and its capabilities known (the first and more obvious one being does it support audio in the first place).
It's nothing new though, maybe it's the error printing itself that is?
Maxime
Hi Maxime,
Am 04.06.21 um 11:02 schrieb Maxime Ripard:
Hi Stefan,
I would assume it's due to this: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/driv...
It pre-dates my time working on the vc4 driver so I'm not really sure what this is supposed to prevent, but my guess is that it's there to avoid someone using the audio card before we have a display detected and connected, and its capabilities known (the first and more obvious one being does it support audio in the first place).
It's nothing new though, maybe it's the error printing itself that is?
i'm sorry, i forgot about this discussion here:
https://lists.freedesktop.org/archives/dri-devel/2020-December/292701.html
Regards Stefan
Maxime
Hi Stefan,
On Sat, Jun 12, 2021 at 12:04:08PM +0200, Stefan Wahren wrote:
Hi Maxime,
Am 04.06.21 um 11:02 schrieb Maxime Ripard:
Hi Stefan,
I would assume it's due to this: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/driv...
It pre-dates my time working on the vc4 driver so I'm not really sure what this is supposed to prevent, but my guess is that it's there to avoid someone using the audio card before we have a display detected and connected, and its capabilities known (the first and more obvious one being does it support audio in the first place).
It's nothing new though, maybe it's the error printing itself that is?
i'm sorry, i forgot about this discussion here:
https://lists.freedesktop.org/archives/dri-devel/2020-December/292701.html
It looks like there's no discussion on that link, is it the link you wanted to paste?
Maxime
Hi Maxime,
Am 17.06.21 um 17:25 schrieb Maxime Ripard:
Hi Stefan,
On Sat, Jun 12, 2021 at 12:04:08PM +0200, Stefan Wahren wrote:
Hi Maxime,
Am 04.06.21 um 11:02 schrieb Maxime Ripard:
Hi Stefan,
I would assume it's due to this: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/driv...
It pre-dates my time working on the vc4 driver so I'm not really sure what this is supposed to prevent, but my guess is that it's there to avoid someone using the audio card before we have a display detected and connected, and its capabilities known (the first and more obvious one being does it support audio in the first place).
It's nothing new though, maybe it's the error printing itself that is?
i'm sorry, i forgot about this discussion here:
https://lists.freedesktop.org/archives/dri-devel/2020-December/292701.html
It looks like there's no discussion on that link, is it the link you wanted to paste?
it was the right patch, but the discussion get lost because of turn of the year. Next try:
https://www.spinics.net/lists/dri-devel/msg284535.html
Maxime
On Thu, Jun 17, 2021 at 07:41:09PM +0200, Stefan Wahren wrote:
Hi Maxime,
Am 17.06.21 um 17:25 schrieb Maxime Ripard:
Hi Stefan,
On Sat, Jun 12, 2021 at 12:04:08PM +0200, Stefan Wahren wrote:
Hi Maxime,
Am 04.06.21 um 11:02 schrieb Maxime Ripard:
Hi Stefan,
I would assume it's due to this: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/driv...
It pre-dates my time working on the vc4 driver so I'm not really sure what this is supposed to prevent, but my guess is that it's there to avoid someone using the audio card before we have a display detected and connected, and its capabilities known (the first and more obvious one being does it support audio in the first place).
It's nothing new though, maybe it's the error printing itself that is?
i'm sorry, i forgot about this discussion here:
https://lists.freedesktop.org/archives/dri-devel/2020-December/292701.html
It looks like there's no discussion on that link, is it the link you wanted to paste?
it was the right patch, but the discussion get lost because of turn of the year. Next try:
It looks like Mark wasn't particularly on-board with that change though :/
I'm not really sure what to do with it, really. The only issue I'm seeing is that there's some logging that doesn't look too nice. Is there anything else?
Maxime
Am 28.06.21 um 14:28 schrieb Maxime Ripard:
On Thu, Jun 17, 2021 at 07:41:09PM +0200, Stefan Wahren wrote:
Hi Maxime,
Am 17.06.21 um 17:25 schrieb Maxime Ripard:
Hi Stefan,
On Sat, Jun 12, 2021 at 12:04:08PM +0200, Stefan Wahren wrote:
Hi Maxime,
Am 04.06.21 um 11:02 schrieb Maxime Ripard:
Hi Stefan,
I would assume it's due to this: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/driv...
It pre-dates my time working on the vc4 driver so I'm not really sure what this is supposed to prevent, but my guess is that it's there to avoid someone using the audio card before we have a display detected and connected, and its capabilities known (the first and more obvious one being does it support audio in the first place).
It's nothing new though, maybe it's the error printing itself that is?
i'm sorry, i forgot about this discussion here:
https://lists.freedesktop.org/archives/dri-devel/2020-December/292701.html
It looks like there's no discussion on that link, is it the link you wanted to paste?
it was the right patch, but the discussion get lost because of turn of the year. Next try:
It looks like Mark wasn't particularly on-board with that change though :/
I'm not really sure what to do with it, really. The only issue I'm seeing is that there's some logging that doesn't look too nice. Is there anything else?
No, nothing i know.
Regards
Maxime
participants (2)
-
Maxime Ripard -
Stefan Wahren