From: Phillip Susi <psusi@cfl.rr.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Automatic S1 sleep
Date: Tue, 11 May 2010 14:18:01 -0400 [thread overview]
Message-ID: <4BE99F59.1010100@cfl.rr.com> (raw)
In-Reply-To: <20100511171900.GA17704@srcf.ucam.org>
On 5/11/2010 1:19 PM, Matthew Garrett wrote:
> You'll need wakeup events on mouse, keyboard, network packets and so on.
> Some of these are possible, some aren't really.
On some systems, yes, but generally these are widely possible. Last
night I experimented with S1 on my desktop pc and after using ethtool to
enable wake on lan, the system slept for several seconds, then woke up
when someone spoke on IRC, causing a packet to hit the NIC. Another
machine I have here has an Intel e100 series NIC and it appears that the
driver for it only supports wake on magic packet, though I checked the
Intel specs on the chip and it is capable of the other wol modes.
> Just have suspend_devices_and_enter conditionalise the device suspend on
> whether or not it's PM_SUSPEND_STANDBY.
Ahh, that looks like the place. Is there a reason why it does not
already do that?
Also Documentation/power/states.txt says that S1 puts devices that
support it into D1. I would think the code to do that would be here in
suspend_devices_and_enter() but I don't see it. Do you know where that
is? I checked and my ATI Radeon video card supports D1 and D2 so could
potentially save a good bit of power by using these states.
next prev parent reply other threads:[~2010-05-11 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 16:03 Automatic S1 sleep Phillip Susi
2010-05-11 17:19 ` Matthew Garrett
2010-05-11 18:18 ` Phillip Susi [this message]
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=4BE99F59.1010100@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.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).