On Mon, 2005-03-07 at 11:42 -0500, Alan Stern wrote:
> On Mon, 7 Mar 2005, ee21rh wrote:
>
> > Hi. I've been working alongside other HAL developers working on
> > PowerManagement userspace policy for computers and laptops using
> > HAL and DBUS. Nigel Cunningham recently told me of this lists existence,
> > and I told him I would share with you guys what we have been doing.
>
> > If you have any comments/ideas or would like to help then please email me
> > a reply, or post on the Wiki.
> >
> > I hope that some of you linux-pm people and the HAL people can work
> > together to provide a "Just Works" solution to power management on
> > computers and laptops.
>
> Of greatest importance to us would be to know what facilities your project
> needs the kernel to provide, particularly for peripheral power management.
> As yet there isn't an agreed-upon design, and it would help to know what
> users will want.
That's a pretty difficult question to answer - I guess the most
important for user space is having a uniform interface to the kernel
that it easy to use.
That's pretty broad, I realize that, to me it means
- sysfs interface
- asynchronous change notification using e.g. uevents
- this is both per device but also for things like "Not enough
power to use USB device XYZ" (both Windows and OS X does this)
- IIRC we currently lack this for e.g. ACPI suspend/resume
- ideally bus-independent; that is using the same names for power
states not dependent on what bus type a device is on
- sane default policy
- it should be the exception that user space overrides default policy
As to the UI, I don't expect end users to fiddle around with anything
specific, but I do expect sysadmins would like the following per-device
settings such as
[x] Allow this device to wake up computer
[x] Allow computer to bring this device into low power mode
That's all I can think of now, sorry if it's not more useful.
Thanks,
David
