intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: linux-kernel@vger.kernel.org
Cc: rjw@sisk.pl, intel-gfx@lists.freedesktop.org
Subject: VT switchless suspend/resume
Date: Sat,  2 Feb 2013 16:34:07 +0100	[thread overview]
Message-ID: <1359819248-3714-1-git-send-email-jbarnes@virtuousgeek.org> (raw)

Finally got around to updating these patches here at FOSDEM.  I made the
core PM support for this into a function so multiple drivers can
indicate their support and we'll be conservative about doing the switch
if no drivers call in or if any driver indicates it can't support VT
switchless suspend/resume.  Please check the logic in my
pm_vt_switch_required function; I try to handle several cases:
  1) no driver calls the routine (should VT switch)
  2) driver requires it but then unbinds and clears its req, a
     subsequent driver that doesn't require VT switching should have its
     switchless behavior honored (shouldn't VT switch)
  3) multiple drivers call in with different reqs (should VT switch)
  4) multiple or single drivers call in that don't require VT switching
     (shouldn't VT switch)

Still need to add calls to some other drivers, so if this looks ok I can
do that.

Thanks,
Jesse

             reply	other threads:[~2013-02-02 15:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-02 15:34 Jesse Barnes [this message]
2013-02-02 15:34 ` [PATCH] PM: make VT switching to the suspend console optional v2 Jesse Barnes
2013-02-02 19:39   ` Rafael J. Wysocki
2013-02-02 20:50     ` Rafael J. Wysocki
2013-02-03  8:56       ` Jesse Barnes
2013-02-03 12:59         ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2013-02-19 20:11 VT switchless suspend/resume Jesse Barnes
2013-02-19 21:25 ` Paulo Zanoni
2013-02-25 19:19   ` Paulo Zanoni
2013-02-25 21:31     ` Jesse Barnes
2013-03-07 16:38       ` 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=1359819248-3714-1-git-send-email-jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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).