From: Takashi Iwai <tiwai@suse.de>
To: "Lin, Mengdong" <mengdong.lin@intel.com>
Cc: "Yang, Libin" <libin.yang@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: [PATCH 1/2] ALSA: hda - Continue probing even if i915 binding fails
Date: Fri, 12 Jun 2015 07:08:36 +0200 [thread overview]
Message-ID: <s5hmw057bu3.wl-tiwai@suse.de> (raw)
In-Reply-To: <F46914AEC2663F4A9BB62374E5EEF8F82B88A8E4@SHSMSX101.ccr.corp.intel.com>
At Fri, 12 Jun 2015 02:08:50 +0000,
Lin, Mengdong wrote:
>
> > -----Original Message-----
> > From: Takashi Iwai [mailto:tiwai@suse.de]
> > Sent: Wednesday, June 10, 2015 6:26 PM
> >
> > Currently snd-hda-intel driver aborts the probing of Intel HD-audio controller
> > with i915 power well management when binding with i915 driver via
> > hda_i915_init() fails. This is no big problem for Haswell and Broadwell where
> > the HD-audio controllers are dedicated to HDMI/DP, thus i915 link is
> > mandatory. However, Skylake, Baytrail and Braswell have only one controller
> > and both HDMI/DP and analog codecs share the same bus. Thus, even if
> > HDMI/DP isn't usable, we should keep the controller working for other codecs.
> >
> > For fixing this, this patch simply allows continuing the probing even if
> > hda_i915_init() call fails. This may leave stale sound components for
> > HDMI/DP devices that are unbound with graphics. We could abort the
> > probing selectively, but from the code simplicity POV, it's better to continue in
> > all cases.
> >
> > Reported-by: Libin Yang <libin.yang@intel.com>
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > ---
> > This is for 4.1. Appying to 4.2 may result in trivial conflicts.
> >
> > sound/pci/hda/hda_intel.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c index
> > fea198c58196..8a0af6770e1d 100644
> > --- a/sound/pci/hda/hda_intel.c
> > +++ b/sound/pci/hda/hda_intel.c
> > @@ -1855,7 +1855,7 @@ static int azx_probe_continue(struct azx *chip)
> > #ifdef CONFIG_SND_HDA_I915
> > err = hda_i915_init(hda);
> > if (err < 0)
> > - goto out_free;
> > + goto skip_i915;
> > err = hda_display_power(hda, true);
> > if (err < 0) {
> > dev_err(chip->card->dev,
> > @@ -1865,6 +1865,7 @@ static int azx_probe_continue(struct azx *chip)
> > #endif
> > }
> >
> > + skip_i915:
> > err = azx_first_init(chip);
> > if (err < 0)
> > goto out_free;
> > --
> > 2.4.3
>
> Thanks for your patch. But maybe we should not skip i915 for the dedicated
> display HD-A controller on Haswell/Broadwell.
>
> For HSW/BDW, their HD-A controller for display audio (PCI dev#3) is *partly*
> in GPU power domain:
> - Its PCI configuration space is out of i915 power well, but in an always-on
> power well. So even if the BIOS disables the Intel GPU (PCI dev#2), the HD-A
> controller is still present, and we can still access all standard registers in PCI
> config space.
Right, and changing this doesn't break things.
> - Its audio functions are in the i915 power well. If hda_i915_init() fails and
> I915 power well is unavailable, read/write to the audio register of the
> Controller will fail and we'll get kernel error messages. So I feel it's better
> to abort if hda_i915_init() fails for this HD-A controller.
By skipping, the access to i915 power well won't happen later, since
the component ops isn't set.
I tested Haswell machines with nomodeset to simulate the situation,
and there was no any kernel errors except for the first one indicating
the failure of i915 binding.
I haven't tested Broadwell, though.
thanks,
Takashi
next prev parent reply other threads:[~2015-06-12 5:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 10:26 [PATCH 1/2] ALSA: hda - Continue probing even if i915 binding fails Takashi Iwai
2015-06-10 10:26 ` [PATCH 2/2] ALSA: hda - Allow calling snd_hdac_i915_*() without actual binding Takashi Iwai
2015-06-12 2:08 ` [PATCH 1/2] ALSA: hda - Continue probing even if i915 binding fails Lin, Mengdong
2015-06-12 5:08 ` Takashi Iwai [this message]
2015-06-12 5:50 ` Lin, Mengdong
2015-06-12 6:06 ` Takashi Iwai
2015-06-12 6:17 ` David Henningsson
2015-06-12 6:37 ` Takashi Iwai
2015-06-12 14:14 ` Takashi Iwai
2015-06-12 14:33 ` David Henningsson
2015-06-12 14:36 ` Takashi Iwai
2015-06-12 6:51 ` Lin, Mengdong
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=s5hmw057bu3.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=libin.yang@intel.com \
--cc=mengdong.lin@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.