From: Chris Wilson <chris@chris-wilson.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Suppress hotplug work during PM suspend/resume
Date: Thu, 10 May 2012 11:12:58 +0100 [thread overview]
Message-ID: <1336644799_224010@CP5-2952> (raw)
In-Reply-To: <s5hy5p0xtlm.wl%tiwai@suse.de>
On Thu, 10 May 2012 11:39:49 +0200, Takashi Iwai <tiwai@suse.de> wrote:
> At Thu, 10 May 2012 10:25:44 +0100,
> Chris Wilson wrote:
> >
> > On Thu, 10 May 2012 11:19:11 +0200, Takashi Iwai <tiwai@suse.de> wrote:
> > > At Thu, 10 May 2012 11:06:46 +0200,
> > > Daniel Vetter wrote:
> > > > This patch is not just for hotplug, but for all the delayed work and timer
> > > > stuff the driver does. And we _do_ have a bug report that leaking the rps
> > > > work (for snb+ turbo mode) across either a s/r cycle or a gpu reset kills
> > > > the driver.
> > >
> > > Yes, but my point is that Chris's patch (at least the commit above
> > > alone) won't fix the problem we faced.
> >
> > The patch I thought you two were talking about was:
> > http://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=fastboot&id=a5f91dcc3cb7a9dc1214d5014ea6f0338824ad8e
> > which is what I thought we had planned to fix the residual issue.
>
> Thanks, this explains better :)
>
> But, as far as I checked, the hotplug event wasn't a leftover but
> newly triggered during the resume procedure. Thus there is still a
> race even with the patch [drm/i915: Cancel outstanding modeset workers
> before suspend].
Which should be fixed with Adam's patch to only restore IRQs after doing
the modeset upon resume; if I am following all the threads of this bug
correctly.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-05-10 10:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 16:10 [PATCH] drm/i915: Suppress hotplug work during PM suspend/resume Takashi Iwai
2012-04-19 16:22 ` Chris Wilson
2012-04-19 16:32 ` Takashi Iwai
2012-04-19 16:29 ` Daniel Vetter
2012-04-19 16:38 ` Takashi Iwai
2012-04-19 16:52 ` Daniel Vetter
2012-04-19 17:55 ` Adam Jackson
2012-04-19 18:11 ` Takashi Iwai
2012-04-25 8:14 ` Takashi Iwai
2012-05-10 6:34 ` Takashi Iwai
2012-05-10 8:29 ` Daniel Vetter
2012-05-10 8:40 ` Takashi Iwai
2012-05-10 9:06 ` Daniel Vetter
2012-05-10 9:19 ` Takashi Iwai
2012-05-10 9:25 ` Chris Wilson
2012-05-10 9:39 ` Takashi Iwai
2012-05-10 10:04 ` Daniel Vetter
2012-05-10 10:12 ` Chris Wilson [this message]
2012-05-10 10:13 ` Chris Wilson
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=1336644799_224010@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tiwai@suse.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