From: Peter Clifton <pcjc2@cam.ac.uk>
To: Intel <intel-gfx@lists.freedesktop.org>
Subject: BISECTED: Suspend regression on drm-intel-next
Date: Sat, 18 Dec 2010 20:02:21 +0000 [thread overview]
Message-ID: <1292702541.3071.7.camel@pcjc2lap> (raw)
Hi Chris,
I bisected the suspend regression I mentioned, and came to this commit:
commit 0cdab21f9a1fca50dd27e488839f5a6578e333b2
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Sun Dec 5 17:27:06 2010 +0000
drm/i915: Uncouple render/power ctx before suspending
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Disabling power context tear down on suspend with this diff:
diff --git a/drivers/gpu/drm/i915/i915_suspend.c
b/drivers/gpu/drm/i915/i915_suspend.c
index a311809..6e98764 100644
--- a/drivers/gpu/drm/i915/i915_suspend.c
+++ b/drivers/gpu/drm/i915/i915_suspend.c
@@ -820,7 +820,7 @@ int i915_save_state(struct drm_device *dev)
if (HAS_PCH_SPLIT(dev))
ironlake_disable_drps(dev);
- intel_disable_clock_gating(dev);
+// intel_disable_clock_gating(dev);
/* Cache mode state */
dev_priv->saveCACHE_MODE_0 = I915_READ(CACHE_MODE_0);
NB: I've not tested later than c57802706aad9f179f2219415717896b3c177845,
which does not suspend. (I'm actually pretty certain that I tested until
around a8e93126a6f10d0a14ba8407ec112b1b3a5e2e97, but it was still bad,
and I didn't need to include it in my bisect, I did not make any notes
about it.
Best regards,
--
Peter Clifton
Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA
Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)
next reply other threads:[~2010-12-18 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 20:02 Peter Clifton [this message]
2010-12-18 21:42 ` BISECTED: Suspend regression on drm-intel-next Chris Wilson
2010-12-19 10:05 ` Peter Clifton
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=1292702541.3071.7.camel@pcjc2lap \
--to=pcjc2@cam.ac.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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