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: Wed, 13 Feb 2019 16:56:32 +0100 [thread overview]
Message-ID: <s5h5ztn1y33.wl-tiwai@suse.de> (raw)
In-Reply-To: <da510ed7-269f-e0e9-1d9d-f1ceaad88ef9@molgen.mpg.de>
On Wed, 13 Feb 2019 16:42:19 +0100,
Paul Menzel wrote:
>
> Dear Takashi,
>
>
> On 02/13/19 16:12, Takashi Iwai wrote:
> > On Wed, 13 Feb 2019 15:58:44 +0100,
> > Paul Menzel wrote:
> >>
> >>> Why the i915 driver gets initialized *so late*?
> >>
> >> Maybe, because it’s built as a module?
> >>
> >> ```
> >> $ grep I915 /boot/config-4.20.8.mx64.245
> >> CONFIG_DRM_I915=m
> >> # CONFIG_DRM_I915_ALPHA_SUPPORT is not set
> >> CONFIG_DRM_I915_CAPTURE_ERROR=y
> >> CONFIG_DRM_I915_COMPRESS_ERROR=y
> >> CONFIG_DRM_I915_USERPTR=y
> >> # CONFIG_DRM_I915_GVT is not set
> >> CONFIG_SND_HDA_I915=y
> >> ```
> >
> > That explains. You built the HD-audio as built-in while the graphics
> > as module. This makes the binding impossible at the time of sound
> > driver initialization.
> >
> > If you build the graphics driver as a module, built the sound driver
> > also as a module.
>
> Can this be enforced by the Kconfig configuration?
This is the restriction only needed if i915 HDMI audio is used, so you
can't stop the configuration statically. Your setup would still work
except for HDMI, for example.
> If not, should the
> warning/error message be extended with this hint?
Possible, but why such a weird configuration at the first place...?
Takashi
next prev parent reply other threads:[~2019-02-13 15:56 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
[not found] ` <1d3b00d7-cf62-621c-e972-d732177a4471@molgen.mpg.de>
2018-09-19 18:44 ` 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 [this message]
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=s5h5ztn1y33.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
all inboxes | Powered by JetHome®