From: Takashi Iwai <tiwai@suse.de>
To: Paul Menzel <pmenzel+alsa-devel@molgen.mpg.de>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: snd_hda_codec_hdmi: `hdaudio hdaudioC0D2: Unable to bind the codec`
Date: Tue, 18 Sep 2018 23:00:53 +0200 [thread overview]
Message-ID: <s5h1s9qv7ui.wl-tiwai@suse.de> (raw)
In-Reply-To: <533a0e85-0d03-740d-9f7e-8c29b5cca59f@molgen.mpg.de>
On Tue, 18 Sep 2018 17:55:15 +0200,
Paul Menzel wrote:
>
> Dear Linux folks,
>
>
> With drm-tip (v4.19-rc3-946-g09b295662edd) Linux prints
> `snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel HDMI/DP codec`
> to the log.
>
> ```
> […]
> [ 12.481788] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC671: line_outs=1 (0x21/0x0/0x0/0x0/0x0) type:line
> [ 12.482536] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=1 (0x17/0x0/0x0/0x0/0x0)
> [ 12.483184] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x14/0x0/0x0/0x0/0x0)
> [ 12.483737] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
> [ 12.484198] snd_hda_codec_realtek hdaudioC0D0: inputs:
> [ 12.484582] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19
> [ 12.485100] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18
> [ 12.485519] snd_hda_codec_realtek hdaudioC0D0: Line=0x1a
> [ 12.497685] snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel HDMI/DP codec
> [ 12.498311] hdaudio hdaudioC0D2: Unable to bind the codec
> [ 12.498789] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input6
> [ 12.499567] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input7
> [ 12.500268] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1f.3/sound/card0/input8
> [ 12.501039] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1f.3/sound/card0/input9
> [ 12.501683] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input10
> [ 17.743338] [drm:intel_pch_type [i915]] Found SunrisePoint PCH
> […]
> ```
>
> Is that an error or just a notice?
This must be a side-effect of the recent change in i915 to be async
probe. This made me checking the corresponding ALSA audio binding
code change, and actually found a bug.
Could you try the fix below?
thanks,
Takashi
-- 8< --
From: Takashi Iwai <tiwai@suse.de>
Subject: [PATCH] ALSA: hda: Fix the audio-component completion timeout
The timeout of audio component binding was incorrectly specified in
msec, not in jiffies, which results in way too shorter timeout than
expected.
Along with fixing it, add the information print about the binding
failure to show the unexpected situation more clearly.
Fixes: a57942bfdd61 ("ALSA: hda: Make audio component support more generic")
Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
sound/hda/hdac_i915.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/sound/hda/hdac_i915.c b/sound/hda/hdac_i915.c
index b5282cbbe489..617ff1aa818f 100644
--- a/sound/hda/hdac_i915.c
+++ b/sound/hda/hdac_i915.c
@@ -145,9 +145,11 @@ int snd_hdac_i915_init(struct hdac_bus *bus)
if (!acomp->ops) {
request_module("i915");
/* 10s timeout */
- wait_for_completion_timeout(&bind_complete, 10 * 1000);
+ wait_for_completion_timeout(&bind_complete,
+ msecs_to_jiffies(10 * 1000));
}
if (!acomp->ops) {
+ dev_info(bus->dev, "couldn't bind with audio component\n");
snd_hdac_acomp_exit(bus);
return -ENODEV;
}
--
2.18.0
next parent reply other threads:[~2018-09-18 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <533a0e85-0d03-740d-9f7e-8c29b5cca59f@molgen.mpg.de>
2018-09-18 21:00 ` Takashi Iwai [this message]
[not found] ` <1d3b00d7-cf62-621c-e972-d732177a4471@molgen.mpg.de>
2018-09-19 18:44 ` snd_hda_codec_hdmi: `hdaudio hdaudioC0D2: Unable to bind the codec` Takashi Iwai
2019-02-13 14:58 ` Paul Menzel
2019-02-13 15:12 ` Takashi Iwai
2019-02-13 15:42 ` Paul Menzel
2019-02-13 15:56 ` Takashi Iwai
2019-02-14 16:00 ` Paul Menzel
2019-02-14 16:06 ` Takashi Iwai
2019-02-18 15:17 ` Paul Menzel
2019-02-18 15:38 ` Takashi Iwai
2019-02-18 15:40 ` Paul Menzel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5h1s9qv7ui.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel+alsa-devel@molgen.mpg.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox