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:43:25 -0400 [thread overview]
Message-ID: <4BE9A54D.2060500@cfl.rr.com> (raw)
In-Reply-To: <20100511182129.GA19264@srcf.ucam.org>
On 5/11/2010 2:21 PM, Matthew Garrett wrote:
> 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.
Sounds reasonable. Maybe I'll take a crack at writing a patch to do that.
> 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.
Actually after looking at some ATI specs it seems that there are several
configuration options of exactly what should be powered down in D1 and
D2 but the DAC output did not seem to be one of them. It seems to be
intended to do things like stop the GPU clocks but otherwise leave the
display on. I assumed that the card was in D1 last night while the
system was in S1, and the display remained visible. If D1 does stop the
DVI output then it must not have been set to D1.
How does the PCI core get called when changing state? I would think it
would be when suspend_devices_and_enter() calls
dpm_suspend_start(PMESG_SUSPEND) but that does not differentiate between
S1 and S3, so I would think that currently it would result in placing
the device in D3, and that if I remove the PMESG_SUSPEND for
PM_SUSPEND_STANDBY that it would result in leaving devices in D0.
next prev parent reply other threads:[~2010-05-11 18:43 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
2010-05-11 18:43 ` Phillip Susi [this message]
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=4BE9A54D.2060500@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).