From: Matthew Garrett <mjg59@srcf.ucam.org>
To: David Brownell <david-b@pacbell.net>
Cc: lenb@kernel.org, "linux-acpi@vger" <linux-acpi@vger.kernel.org>,
linux-pm@lists.osdl.org, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [linux-pm] [PATCH 3/6] [-mm]: ACPI: duplicate ACPI sleep "alarm" attribute in sysfs
Date: Mon, 8 Jan 2007 20:43:17 +0000 [thread overview]
Message-ID: <20070108204317.GA24181@srcf.ucam.org> (raw)
In-Reply-To: <200701081239.08687.david-b@pacbell.net>
On Mon, Jan 08, 2007 at 12:39:08PM -0800, David Brownell wrote:
> In that current API there's no way to tell anything at all about the
> target system state inside a driver's suspend() method. So if there
> were some characteristic of S4 (or S3 etc) that mattered to the driver
> (it should test for the attribute, not S4/etc since S4 is ACPI-specific)
> the driver couldn't do anything about it ... so as I said, not useful.
Well, it's not just a matter for the driver - in terms of userspace UI,
we want to be able to expose which wakeup events will work in suspend to
disk. If the API can't currently expose that, then we probably want to
look into ways of fixing that.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2007-01-08 20:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 11:35 [PATCH 3/6] [-mm]: ACPI: duplicate ACPI sleep "alarm" attribute in sysfs Zhang Rui
2007-01-06 22:42 ` David Brownell
2007-01-07 5:57 ` [linux-pm] " Matthew Garrett
2007-01-08 2:31 ` David Brownell
2007-01-08 10:10 ` Matthew Garrett
2007-01-08 20:39 ` David Brownell
2007-01-08 20:43 ` Matthew Garrett [this message]
2007-01-08 21:15 ` David Brownell
2007-01-08 10:13 ` Zhang Rui
2007-01-08 20:46 ` David Brownell
2007-01-07 11:19 ` Pavel Machek
2007-01-08 3:44 ` David Brownell
2007-01-08 11:36 ` Pavel Machek
2007-01-08 20:35 ` David Brownell
2007-01-25 4:21 ` Len Brown
2007-01-25 9:39 ` [linux-pm] " David Brownell
2007-01-25 19:47 ` Pavel Machek
2007-01-25 23:12 ` Len Brown
2007-01-25 23:28 ` Nigel Cunningham
2007-01-26 0:33 ` David Brownell
2007-01-26 17:07 ` Pavel Machek
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=20070108204317.GA24181@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=david-b@pacbell.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=rui.zhang@intel.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).