Re: [ACPI] PATCH-ACPI based CPU hotplug[2/6]-ACPI Eject interface support

From: Dmitry Torokhov <dtor_core_at_ameritech.net>
Date: 2004-09-21 11:20:05
On Monday 20 September 2004 07:52 pm, Alex Williamson wrote:
> On Mon, 2004-09-20 at 18:12 -0500, Dmitry Torokhov wrote: 
> > 
> > Hi Anil,
> > 
> > I obviously failed to deliver my idea :) I meant that I would like add eject
> > attribute (along with maybe status, hid and some others) to kobjects in
> > /sys/firmware/acpi tree.
> > 
> 
> Dmitry,
> 
>    See the patch I just posted to acpi-devel and lkml (Subject:
> [PATCH/RFC] exposing ACPI objects in sysfs).  It exposes acpi objects as
> you describe.   Something simple like:
> 
>  # cat /sys/firmware/acpi/namespace/ACPI/_SB/LSB0/_EJ0
> 
> Will call the _EJ0 method on the ACPI device.  You can evaluate eject
> dependencies using the _EJD method.
> 
> 	Alex
> 

Alex,

While I think that your patch is very important and should be included (maybe
if not as is if somebody has some objections but in some other form) I see it
more like developer's tool. I imagined status, HID, eject etc. attributes to
be sanitized interface to kernel's data, not necessarily causing re-evaluation.

So it could be like this:

/sys/firmware/acpi/namespace/ACPI/_SB/LSB0/status
/sys/firmware/acpi/namespace/ACPI/_SB/LSB0/removable
/sys/firmware/acpi/namespace/ACPI/_SB/LSB0/lockable
..
/sys/firmware/acpi/namespace/ACPI/_SB/LSB0/eject

And your raw access to the ACPI methods could reside under raw:

/sys/firmware/acpi/namespace/ACPI/_SB/LSB0/raw/_STA
/sys/firmware/acpi/namespace/ACPI/_SB/LSB0/raw/_RNV
/sys/firmware/acpi/namespace/ACPI/_SB/LSB0/raw/_LCK
..
/sys/firmware/acpi/namespace/ACPI/_SB/LSB0/raw/_EJ0

-- 
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Mon Sep 20 21:20:39 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:30 EST