public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Thomas Renninger <trenn@suse.de>,
	linux-acpi@vger.kernel.org, "Brown, Len" <len.brown@intel.com>,
	"Li, Shaohua" <shaohua.li@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 16:13:41 +0800	[thread overview]
Message-ID: <1164183221.5461.41.camel@localhost.localdomain> (raw)
In-Reply-To: <20061121163438.GA16748@srcf.ucam.org>

On Tue, 2006-11-21 at 16:34 +0000, Matthew Garrett wrote:
> (I seem to be missing the original mail here...)
> 
> On Mon, Nov 20, 2006 at 12:18:13PM +0100, Thomas Renninger 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...
> 
> This should presumably just be handled by the clock driver rather than 
> the ACPI subsystem. There's only a tiny amount of acpi-related code in 
> the driver, and that's information that we could just export to the 
> clock instead.
> 
I prefer to locate "alarm" under /sys/power, together with "wakeup".
Yes, you are right that it does have a lot to do with the clock driver.
But I think this patch series should impact other parts little. You
know, the main purpose of this patch series is just to duplicate the
procfs function in sysfs. So only the functions for sysfs interface will
be added in the first step. :)
-
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

  reply	other threads:[~2006-11-22  8:10 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 [this message]
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
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=1164183221.5461.41.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=mjg59@srcf.ucam.org \
    --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