Bluetooth and power stuff
Richard Hughes
hughsient at gmail.com
Tue May 2 02:40:17 PDT 2006
On Mon, 2006-05-01 at 14:27 -0400, David Zeuthen wrote:
> with methods for doing this. I *think* we want to export this interface
> on bus devices, e.g. (snippet from lshal -t)
Yes, this is exactly what we want.
> Now, the big question is what methods do the interface
>
> org.freedesktop.Hal.Device.DevicePowerManagement
>
> implement. It should satisfy
>
> - Must be able to put the device to sleep
>
> - Must be able to power off the device (to comply with FAA/FCC
> requirements)
>
> - Must be able to power up a device
>
> - Control aspects of run-time power management policy (should be
> enforced by the kernel, e.g. transparently put the sound card to
> sleep when no one has open fd's on it)
>
> - Should be the same interface across USB, PCI, whatever, hence it
> needs to be somewhat extensible and needs to be somewhat abstract
> (e.g. we PCI power states like D1-D3 won't work on USB)
What about:
PowerUp()
PowerDown()
PowerSuspend()
How about adding the capability with the fdi files -- for instance a
wireless adaptor supports on and off, but a usb hub can suspend but not
power down.
Doesn't acpi provide us with the sleep states per device on a new-ish
kernel? e.g.
echo -n $state > /sys/bus/pci/devices/$foo/power/state
For me I get the current state for (my on-board ethernet):
cat /sys/bus/pci/devices/0000\:01\:08.0/power/state
> but I don't really know what it's going to look like as I'm not sure the
> Linux kernel guys have settled on the format yet. And it raises the
> question of how this is going to work on Solaris and FreeBSD too :-)
Let us implement it for Linux, then they get jealous and want a bit of
the action. :-)
Richard.
More information about the hal
mailing list