From: Zhang Rui <rui.zhang@intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>,
David Brownell <david-b@pacbell.net>
Cc: linux-pm@lists.osdl.org, lenb@kernel.org,
"linux-acpi@vger" <linux-acpi@vger.kernel.org>,
linux-pm@osdl.org
Subject: Re: [linux-pm] [PATCH 0/6] [-mm]: ACPI: duplicate ACPI procfs functions in sysfs
Date: Mon, 08 Jan 2007 19:40:28 +0800 [thread overview]
Message-ID: <1168256428.5754.98.camel@localhost.localdomain> (raw)
In-Reply-To: <20070107055424.GA24853@srcf.ucam.org>
On Sun, 2007-01-07 at 05:54 +0000, Matthew Garrett wrote:
> On Sat, Jan 06, 2007 at 02:21:41PM -0800, David Brownell wrote:
>
> > Please tell me you mean "devices with a /sys/devices/.../power/wakeup"
> > attribute. And that ACPI is finally going to start working with those
> > attributes ...
>
> It's not necessarily possible to map from an ACPI object with a wakeup
> capability to a Linux device, so there's going to have to be some degree
> of interface nastiness. However, some devices can be sensibly mapped,
> and ideally those should be integrated into
> /sys/devices/.../power/wakeup.
I do want to integrate this ACPI sleep wakeup attribute
into /sys/devices/.../power/wakeup.
But this needs some changes in driver core to make ACPI work properly.
And this will be done in further patches.
I think I forgot some introductions about the background of this patch
set in [PATCH 0/6].
This patch set is against acpi-test sysfs branch which already converts
ACPI to follow driver model. Now the ACPI procfs functions are
duplicated in sysfs step by step. And I want the ACPI interface in sysfs
works exactly the same way as in procfs.
So, currently I don't want too many parts are involved until this branch
is proved to work stable. Or else, you know, it would be painful to dig
out what the problem is if something breaks.
BTW: it's true that the "alarm" can not handle multiple RTCs though it
works in the same way as /proc/acpi/alarm. But
if /sys/class/rtc/rtcN/alarm can provide the same function, it's great
and I'll drop patch#03. I'll also mark /proc/acpi/alarm as deprecated if
David's patches are merged. :)
Thanks,
Rui
next prev parent reply other threads:[~2007-01-08 11:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 11:35 [PATCH 0/6] [-mm]: ACPI: duplicate ACPI procfs functions in sysfs Zhang Rui
2007-01-06 22:21 ` David Brownell
2007-01-07 5:54 ` [linux-pm] " Matthew Garrett
2007-01-08 3:31 ` David Brownell
2007-01-08 13:10 ` Pavel Machek
2007-01-25 4:14 ` Len Brown
2007-01-25 5:50 ` Matthew Garrett
2007-01-25 9:35 ` David Brownell
2007-01-08 11:40 ` Zhang Rui [this message]
2007-01-08 13:13 ` Pavel Machek
2007-01-25 2:28 ` Len Brown
2007-01-25 12:08 ` Pavel Machek
2007-01-25 13:15 ` David Brownell
2007-01-25 19:51 ` Pavel Machek
2007-01-26 1:36 ` Zhang Rui
2007-01-10 20:53 ` David Brownell
2007-01-25 4:17 ` Len Brown
2007-01-25 13:15 ` Pavel Machek
2007-01-25 3:33 ` [linux-pm] " Len Brown
2007-01-25 3:28 ` Len Brown
2007-01-25 9:54 ` David Brownell
2007-01-25 19:37 ` Pavel Machek
2007-01-07 11:15 ` Pavel Machek
2007-01-25 2:03 ` Len Brown
2007-01-25 2:52 ` Nigel Cunningham
2007-01-25 8:17 ` Rafael J. Wysocki
2007-01-25 10:00 ` [linux-pm] " David Brownell
2007-01-18 6:53 ` Zhang Rui
2007-01-21 5:48 ` [PATCH 0/3] " Zhang Rui
2007-01-25 3:50 ` Len Brown
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=1168256428.5754.98.camel@localhost.localdomain \
--to=rui.zhang@intel.com \
--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=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).