public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Suspend/resume without VT switches
Date: Fri, 02 Nov 2012 22:51:07 +0100	[thread overview]
Message-ID: <7608326.fQBj17U8Wv@vostro.rjw.lan> (raw)
In-Reply-To: <1351892621-4840-1-git-send-email-jbarnes@virtuousgeek.org>

On Friday, November 02, 2012 02:43:39 PM Jesse Barnes wrote:
> I've lightly tested this with X and it definitely makes my
> suspend/resume sequence a bit prettier.  It should speed things up
> trivally as well, but most of those gains come from other changes to the
> i915 driver (posted earlier to intel-gfx).
> 
> Any thoughts?

I like the idea.

> I suspect we'll have to be more defensive about the
> resume configuration in case the BIOS did something weird, but overall I
> think we should be able to do this one way or another.

Perhaps patch [1/2] should be [2/2] and vice versa? :-)

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  parent reply	other threads:[~2012-11-02 21:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02 21:43 [RFC] Suspend/resume without VT switches Jesse Barnes
2012-11-02 21:43 ` [PATCH 1/2] PM: make VT switching to the suspend console optional Jesse Barnes
2012-11-02 23:43   ` Alan Cox
2012-11-03  0:20     ` Jesse Barnes
2012-11-03  0:42       ` Alan Cox
2012-11-03  0:40         ` Jesse Barnes
2012-11-02 21:43 ` [PATCH 2/2] drm/i915: support resume without VT switch Jesse Barnes
2012-11-02 21:51 ` Rafael J. Wysocki [this message]
2012-11-02 23:29   ` [RFC] Suspend/resume without VT switches Jesse Barnes
2012-11-02 23:38     ` Rafael J. Wysocki
2012-11-03  0:22       ` Jesse Barnes

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=7608326.fQBj17U8Wv@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.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