linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: linux-acpi@vger.kernel.org
Subject: Automatic S1 sleep
Date: Tue, 11 May 2010 12:03:21 -0400	[thread overview]
Message-ID: <4BE97FC9.4040302@cfl.rr.com> (raw)

I have been looking into the possibility of having the system
automatically enter and exit S1 to save power when idle, but actively in
use.  For instance, while you are only browsing the web on your laptop,
your eyes spend 15 seconds scanning the page while the system is
otherwise, doing nothing but wait for your next input.  It would be nice
if it could seamlessly enter S1 during this time to save power, and exit
when you press a key, move the mouse, or receive a message on IRC.

Unlike S3, S1 keeps the Vcc power plane on and all devices remain in D0
or D1, so the screen remains on and visible, so it should be possible to
use this state transparently without the user even being aware of it.
Since everything remains on, no hardware needs reinitialized when
resuming from S1.  Here seems to be a problem with the current kernel code:

It seems that the generic pm core code defined the PM_EVENT_SUSPEND
state with S3 in mind, and so hardware drivers are notified of
PM_EVENT_SUSPEND and reinitialized when resuming, assuming that the
hardware lost power.  When using acpi S1, this reinitialization activity
is not required and should not be done, so it seems that S1 should not
generate PM_EVENT_SUSPEND and PM_EVENT_RESUME events.

Does anyone have any thoughts on my conclusion or advice on how to
trigger S1 without generating PM_EVENT_SUSPEND?

             reply	other threads:[~2010-05-11 16:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 16:03 Phillip Susi [this message]
2010-05-11 17:19 ` Automatic S1 sleep Matthew Garrett
2010-05-11 18:18   ` Phillip Susi
2010-05-11 18:21     ` Matthew Garrett
2010-05-11 18:43       ` Phillip Susi
2010-05-11 20:19         ` Phillip Susi
2010-05-12  5:57 ` Len Brown
2010-05-12 13:39   ` Phillip Susi
2010-05-20  4:07     ` Len Brown
2010-05-20 13:51       ` Phillip Susi

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=4BE97FC9.4040302@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=linux-acpi@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;
as well as URLs for NNTP newsgroup(s).