From: Zhang Rui <rui.zhang@intel.com>
To: Shaohua Li <shaohua.li@intel.com>, trenn@suse.de
Cc: linux-acpi@vger.kernel.org, "Brown, Len" <len.brown@intel.com>,
"Yu, Luming" <luming.yu@intel.com>,
Kay Sievers <kasievers@suse.de>
Subject: Re: problems about ACPI sysfs convert work
Date: Wed, 22 Nov 2006 15:53:47 +0800 [thread overview]
Message-ID: <1164182027.5461.22.camel@localhost.localdomain> (raw)
In-Reply-To: <1164158892.3551.3.camel@sli10-conroe.sh.intel.com>
On Wed, 2006-11-22 at 09:28 +0800, Shaohua Li wrote:
> On Mon, 2006-11-20 at 12:18 +0100, Thomas Renninger wrote:
> > On Mon, 2006-11-20 at 18:10 +0800, Zhang, Rui wrote:
> > > Hello, lists
> > > I’m doing the ACPI sysfs convert work now. And I have some problems when duplicating some procfs interfaces to sysfs.
> > > Under driver model (this will be available soon), files under /proc/acpi/xxx(driver)/yyy(device)/ will be duplicated under /sys/device/ as they are properties of individual devices.
> > > But I still have some trouble on dealing with the files under /prco/acpi, including “alarm”, “sleep”, “wakeup”, “debug_layer”, “debug_level”, “dsdt”, “fadt”, “event” and “info”.
> > > Following is a proposal as well as some problem and I’m not quite sure about the places all these attributes should be located at. I wish to get some advice from you, and any comment is welcome☺.
> > >
> > > 1. Where should “alarm” be located? Another problem is whether we should put a duration into this file instead of a future time.
> > Don't know, never used...
> > > 2. “sleep” is already marked as deprecated because /sys/power/state has the same function. I won’t do the repeated work again.
> > Yep.
> > > 3. “wakeup” should not exist, but be an attribute of individual devices kobjects.
> > Maybe the devices can be linked
> > like /sys/.../wakeup/${links_to_wakeup_devices}
> > So that userspace does not need to search over the whole device tree to
> > find them?
Sounds great. I'll have a try.
> Sounds like a good idea. But this should be done in driver core. Other
> devices like pci might support wakeup too. device declaims to support
> wakeup, and driver core create a link to /sys/.../wakeup/xxx. I'd
> suggest don't do this in acpi part.
>
Yes. That makes sense. But I don't want too many files to be involved,
especially at the beginning. :). This should be done in another patch in
the future if everything goes well.
Thanks,
Ray
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-11-22 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58A36151585E4047913F40517D307BAE01719E@pdsmsx404.ccr.corp.intel.com>
2006-11-20 11:18 ` problems about ACPI sysfs convert work Thomas Renninger
2006-11-21 16:34 ` Matthew Garrett
2006-11-22 8:13 ` Zhang Rui
2006-11-23 2:29 ` Len Brown
2006-11-22 22:12 ` Len Brown
2006-11-22 22:25 ` Matthew Garrett
2006-11-22 1:28 ` Shaohua Li
2006-11-22 7:53 ` Zhang Rui [this message]
2006-11-22 10:49 ` Thomas Renninger
2006-11-22 22:18 ` 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=1164182027.5461.22.camel@localhost.localdomain \
--to=rui.zhang@intel.com \
--cc=kasievers@suse.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=shaohua.li@intel.com \
--cc=trenn@suse.de \
/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