Patch to hal-spec : 1/6-pmu-acpi
David Zeuthen
david at fubar.dk
Wed Jan 12 16:07:07 PST 2005
OK, so here I assume that all device objects with system.*
properties will also have either acpi.* or pmu.* properties,
right?
On Tue, 2005-01-11 at 18:32 +0000, Richard Hughes wrote:
> <sect2 id="device-properties-pmu">
> <title><literal>pmu</literal> namespace</title>
> <para>
>
> Device objects with the capability pmu represent devices
> currently accessed through the PMU bus /dev/pmu.
How about:
Device objects with the capability pmu represent functionality provided
by the Power Management Unit found in various PPC based systems.
>
> </para>
> <informaltable>
> <tgroup cols="2">
> <thead>
> <row>
> <entry>Key (type)</entry>
> <entry>Values</entry>
> <entry>Mandatory</entry>
> <entry>Description</entry>
> </row>
> </thead>
> <tbody>
> <row>
> <entry><literal>pmu.version</literal> (string)</entry>
> <entry></entry>
> <entry>No</entry>
> <entry>The in-kernel driver version providing PMU services</entry>
> </row>
> </tbody>
> </tgroup>
> </informaltable>
> </sect2>
Should also have pmu.device that gives the device file, e.g. /dev/pmu
(remember, udev may call it something else!).
> <sect2 id="device-properties-acpi">
> <title><literal>acpi</literal> namespace</title>
> <para>
>
> Device objects with the capability <literal>acpi</literal>
> represent devices currently accessed through the ACPI bus
> and found in /proc/acpi
There is, AFAIK, really no ACPI bus; it's a firmware property. Also, one
is not required to mount procfs at /proc :-)
How about
"Device objects with the capability <literal>acpi</literal> represent
functionality accessible through the ACPI firmware"
> represent devices currently accessed through the ACPI bus
> and found in /proc/acpi
>
> </para>
> <informaltable>
> <tgroup cols="2">
> <thead>
> <row>
> <entry>Key (type)</entry>
> <entry>Values</entry>
> <entry>Mandatory</entry>
> <entry>Description</entry>
> </row>
> </thead>
> <tbody>
> <row>
> <entry><literal>acpi.version</literal> (string)</entry>
> <entry>example: 20041210</entry>
> <entry>No</entry>
> <entry>
> The in-kernel driver version providing ACPI
> services
> </entry>
> </row>
> </tbody>
> </tgroup>
> </informaltable>
> </sect2>
Should probably add acpi.proc_path which points to the specific
part of ACPI that we're mapping, e.g. for the device object that
represents power button we would have
acpi.proc_path = /proc/acpi/button/power/PWRF
>
>
> _______________________________________________
> hal mailing list
> hal at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/hal
_______________________________________________
hal mailing list
hal at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/hal
More information about the Hal
mailing list