linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: "linux-acpi@vger" <linux-acpi@vger.kernel.org>, linux-pm@lists.osdl.org
Subject: Re: [PATCH 0/3] [-mm]: ACPI: duplicate ACPI procfs functions in sysfs
Date: Wed, 24 Jan 2007 22:50:20 -0500	[thread overview]
Message-ID: <200701242250.20773.lenb@kernel.org> (raw)
In-Reply-To: <1169358521.5691.2.camel@localhost.localdomain>

On Sunday 21 January 2007 00:48, Zhang Rui wrote:
> This patch set is against acpi-test sysfs branch,
> and will duplicate several ACPI procfs functions in sysfs.
> 
> Patch 01:
> add a Kconfig option to make ACPI procfs configurable.
> This will be used by all the following sysfs conversion patches.

add to feature-removal-schedule-txt
Make it July '07

> Patch 02:
> add ACPI debug attribute in sysfs.
> /proc/acpi/debug_layer && debug_level is deprecated by
> /sys/module/acpi/parameter/debug_layer && debug_level.

I don't think we need feature-removal-schedule-txt since
this is just a debug hook -- can do this right away.

> Patch 03:
> add ACPICA version in sysfs.
> /proc/acpi/info is deprecated by /sys/firmware/acpi/version.

make modparam
 
> Wish list:
> 
> Sysfs interfaces for all the ACPI tables, like the multiple ssdts and
> dynamic loaded ssdts, which are likely to be listed under
> /sys/firmware/acpi/tables/...

agreed.
 
> "wakeup" attribute for ACPI wakeup devices.

first we should nuke the generic wakeup file under devices where
it has no function.

second, the generic wakeup file doesn't give the user any indication
of when it will work.  ie. will it work in S5, or just in S4?
Also, it doesn't give any feedback to show if it is enabled or not.

>         1. Try to map ACPI devices to the physical devices.
>            It's not very easy, as we can not find a generic method to
>            map ACPI wakeup devices to physical devices. So I have to
>            divide them into several groups, e.g. PCI, legacy serial,
>            legacy PS2, etc. And verify which group the ACPI device 
>            belongs to.

Agreed.
PCI is easy, the others may be harder.

>         2. add "wakeup" properly to /sys/device/(not ACPI)/...
>            I'll investigate the possibility of integrating this one into
>            /sys/device/.../power/wakeup.

Agreed.
at the end of the day, we need a single generic wakeup file.
whether the functionality is supplied by ACPI or not should
not be visible to the user.

>         3. consolidate all wakeup devices in one place for convenience.
>            E.g. /sys/power/wakeup/, symbolic links with useful names.
>            (note that links here are from "real" devices node in sysfs,
>            so it's a generic interface for systems both w/ and w/o ACPI)

I think this would be really really useful for user-space --
but then I don't write the utilities, so somebody from that space
might want to weigh in.

>         4. remove /proc/acpi/wakeup,
>            since it's replaced by /sys/power/wakeup/...
> 

thanks,
-Len

      reply	other threads:[~2007-01-25  3:51 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
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 [this message]

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=200701242250.20773.lenb@kernel.org \
    --to=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).