From: Matthew Garrett <mjg59@srcf.ucam.org>
To: David Brownell <david-b@pacbell.net>
Cc: linux-pm@lists.osdl.org, Zhang Rui <rui.zhang@intel.com>,
lenb@kernel.org, "linux-acpi@vger" <linux-acpi@vger.kernel.org>,
linux-pm@osdl.org
Subject: Re: [linux-pm] [PATCH 3/6] [-mm]: ACPI: duplicate ACPI sleep "alarm" attribute in sysfs
Date: Sun, 7 Jan 2007 05:57:57 +0000 [thread overview]
Message-ID: <20070107055757.GB24853@srcf.ucam.org> (raw)
In-Reply-To: <200701061442.22340.david-b@pacbell.net>
On Sat, Jan 06, 2007 at 02:42:22PM -0800, David Brownell wrote:
> On Saturday 06 January 2007 3:35 am, Zhang Rui wrote:
> >
> > Create /sys/power/alarm.
>
> Urg. This doesn't work with the RTC framework, which accepts the reality
> that some systems have multiple RTCs ... /sys/class/rtc/rtcN/alarm is a
> much more appropriate location for that RTC's alarm.
Especially since /proc/acpi/alarm is just banging on the RTC registers
- the only ACPI thing about it is that the FADT can expose whether or
not the extended registers exist, and then making sure that the GPE is
enabled.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2007-01-07 5:58 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 ` Matthew Garrett [this message]
2007-01-08 2:31 ` [linux-pm] " David Brownell
2007-01-08 10:10 ` Matthew Garrett
2007-01-08 20:39 ` David Brownell
2007-01-08 20:43 ` Matthew Garrett
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=20070107055757.GB24853@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=linux-pm@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).