From: David Weinehall <david.weinehall@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Paul Bolle" <pebolle@tiscali.nl>,
"Dirk Griesbach" <spamthis@freenet.de>,
"Jani Nikula" <jani.nikula@intel.com>,
"Mikko Rapeli" <mikko.rapeli@iki.fi>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
stable@vger.kernel.org, "Daniel Vetter" <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org,
"Ilya Tumaykin" <itumaykin@gmail.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: apply the PCI_D0/D3 hibernation workaround everywhere on pre GEN6
Date: Wed, 1 Jul 2015 15:57:02 +0300 [thread overview]
Message-ID: <20150701125702.GW14570@boom> (raw)
In-Reply-To: <20150701123524.GE7969@amd>
On Wed, Jul 01, 2015 at 02:35:24PM +0200, Pavel Machek wrote:
> On Wed 2015-07-01 13:53:31, Ville Syrj�l� wrote:
> > Sure it does. Eventually we'll want to avoid resuming runtime suspended
> > devices when entering system suspend. For broken machines we'd need to
> > resume the GPU at that point.
>
> You want to optimize transition between suspend-to-RAM and
> hibernation? No? I thought so.
>
> So no benefits, 7 real, broken machines.
Runtime suspend = things like S0ix and other forms of shallow sleep.
System suspend = suspend-to-RAM.
It's not about hibernate (though it'd of course nice if a transition
from suspend to hibernate because of low battery won't result in the
device consuming so much battery during the intermediate wakeup that
the device shuts down rather than hibernates).
Kind regards, David
next prev parent reply other threads:[~2015-07-01 12:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 14:06 [PATCH] drm/i915: apply the PCI_D0/D3 hibernation workaround everywhere on pre GEN6 Imre Deak
2015-06-30 17:27 ` Pavel Machek
2015-07-01 8:35 ` Jani Nikula
2015-07-01 8:45 ` Pavel Machek
2015-07-01 9:02 ` Ville Syrjälä
2015-07-01 9:51 ` Pavel Machek
2015-07-01 10:53 ` Ville Syrjälä
2015-07-01 12:35 ` Pavel Machek
2015-07-01 12:42 ` Jani Nikula
2015-07-01 12:57 ` David Weinehall [this message]
2015-07-15 6:22 ` Mikko Rapeli
2015-08-29 18:02 ` Mikko Rapeli
2015-08-31 15:45 ` Jani Nikula
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=20150701125702.GW14570@boom \
--to=david.weinehall@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=itumaykin@gmail.com \
--cc=jani.nikula@intel.com \
--cc=mikko.rapeli@iki.fi \
--cc=pavel@ucw.cz \
--cc=pebolle@tiscali.nl \
--cc=rjw@rjwysocki.net \
--cc=spamthis@freenet.de \
--cc=stable@vger.kernel.org \
--cc=ville.syrjala@linux.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;
as well as URLs for NNTP newsgroup(s).