linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Automatic S1 sleep
Date: Tue, 11 May 2010 19:21:29 +0100	[thread overview]
Message-ID: <20100511182129.GA19264@srcf.ucam.org> (raw)
In-Reply-To: <4BE99F59.1010100@cfl.rr.com>

On Tue, May 11, 2010 at 02:18:01PM -0400, Phillip Susi wrote:
> On 5/11/2010 1:19 PM, Matthew Garrett wrote:
> > 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?

The exact meaning of PM_STANDBY_SUSPEND isn't defined. The sanest 
approach might be to add a callback in the platform_suspend_ops 
structure, pass the sleep state to that and then use that to decide 
whether or not devices need to sleep.

> 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.

Putting a video card into D1 is either going to turn off the output or 
do nothing, so I don't think that's terribly compatible with what you 
want here. But to answer your question, the PCI core will decide what 
state to put devices in based on the sleep type provided.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2010-05-11 18:21 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
2010-05-11 18:21     ` Matthew Garrett [this message]
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=20100511182129.GA19264@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=psusi@cfl.rr.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).