Hello, it's me again...
I'm trying to get a low battery alarm to work on my Eee. In
/sys/class/power_supply/BAT0 I have a good selection of readable
attributes like charge_now, current_now etc. There is also a writeable
"alarm" file. But as far as I can see, the alarm is not implemented.
I have a couple of questions about this:
- Looking at the ACPI battery driver code, it knows that there is no
support for an alarm when it tests the result of evaluating the _BTP
method, which my BIOS doesn't seem to offer. However, it doesn't
subsequently return an error to the write, so my attempt to set an
alarm succeeds. Is this the desired behaviour? Wouldn't it be better
to either not create the alarm file, or to cause writes to fail, when
it's known that there is no support?
- Presumably I could write a trivial daemon to poll the battery level.
A quick search find bazillions of gui applets that do this. I would
prefer to generate a synthetic ACPI battery alarm event when I detect a
low charge level, so that the action taken in response can be
implemented independent of the method of detection. Has this already
been done? Is there an easy way to inject a synthetic ACPI event from
user-space? What does a valid battery alarm event look like?
Many thanks for any suggestions.
Phil.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
