From: Takashi Iwai <tiwai@suse.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Vinod Koul <vinod.koul@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Guneshwor Singh <guneshwor.o.singh@intel.com>,
linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
Julia Lawall <Julia.Lawall@lip6.fr>,
tiwai@suse.de, Hardik T Shah <hardik.t.shah@intel.com>,
"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
Subject: Re: [PATCH] BUG-REPORT: snd-hda: hacked-together EPROBE_DEFER support
Date: Wed, 21 Jun 2017 17:30:10 +0200 [thread overview]
Message-ID: <s5hbmphs6il.wl-tiwai@suse.de> (raw)
In-Reply-To: <149805863799.15021.15278760577807511996@mail.alporthouse.com>
On Wed, 21 Jun 2017 17:23:57 +0200,
Chris Wilson wrote:
>
> Quoting Daniel Vetter (2017-06-21 16:08:54)
> > So back when the i915 power well support landed in
> >
> > commit 99a2008d0b32d72dfc2a54e7be1eb698dd2e3bd6
> > Author: Wang Xingchao <xingchao.wang@linux.intel.com>
> > Date: Thu May 30 22:07:10 2013 +0800
> >
> > ALSA: hda - Add power-welll support for haswell HDA
> >
> > the logic to handle the cross-module depencies was hand-rolled using a
> > async work item, and that just doesn't work.
> >
> > The correct way to handle cross-module deps is either:
> > - request_module + failing when the other module isn't there
> >
> > OR
> >
> > - failing the module load with EPROBE_DEFER.
> >
> > You can't mix them, if you do then the entire load path just
> > busy-spins blowing through cpu cycles forever with no way to stop
> > this.
> >
> > snd-hda-intel does mix it, because the hda codec drivers are loaded
> > using request_module, but the i915 depency is handled using
> > PROBE_DEFER (or well, should be, but I haven't found any code at all).
> > This is a major pain when trying to debug i915 load failures.
> >
> > This patch here is a horrible hackish attempt at somewhat correctly
> > wriing EPROBE_DEFER through. Stuff that's missing:
> > - Check all the other places where load errors are conveniently
> > dropped on the floor.
> > - Also fix up the firmware_cb path.
> > - Drop the debug noise I've left in to make it clear this isn't
> > anything for merging.
>
> This tames "hdaudio hdaudioC0D0: Unable to bind the codec" which was
> continuously spewing previously, and now the system is usable again.
Could you give a failing scenario? I'm not opposing to the suggested
solution, we need to fix the mess in anyway, but I just would like to
know how to trigger the problem easily.
thanks,
Takashi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-06-21 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 15:08 [PATCH] BUG-REPORT: snd-hda: hacked-together EPROBE_DEFER support Daniel Vetter
2017-06-21 15:23 ` Chris Wilson
2017-06-21 15:30 ` Takashi Iwai [this message]
2017-06-26 16:16 ` Daniel Vetter
2017-06-26 17:47 ` Takashi Iwai
2017-06-26 17:54 ` Daniel Vetter
2017-06-28 10:16 ` Takashi Iwai
2017-06-29 10:25 ` Daniel Vetter
2017-07-04 15:14 ` Daniel Vetter
2017-07-04 15:28 ` Takashi Iwai
2017-07-04 18:12 ` Daniel Vetter
2017-06-21 15:52 ` ✗ Fi.CI.BAT: failure for " Patchwork
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=s5hbmphs6il.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Julia.Lawall@lip6.fr \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=guneshwor.o.singh@intel.com \
--cc=hardik.t.shah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=subhransu.s.prusty@intel.com \
--cc=vinod.koul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox