Messages in this thread | | | Date | Fri, 28 Jul 2006 03:35:10 +0300 | From | "Shem Multinymous" <> | Subject | Re: Generic battery interface |
| |
On 7/28/06, Vojtech Pavlik <vojtech@suse.cz> wrote: > note: It's absolutely necessary to limit the API to a well usable > SUBSET of a superset of the features of all drivers/devices, > even sacrificing obscure features to keep the API sane. One > example would be the HID Power spec, which simply can't be > supported to full extent by any sane API.
Non-standard functions must be handled reasonably within the framework, otherwise drivers will have to build duplicate interfaces.
How about /sys/whatever/battery0/voltage for standard attributes and /sys/whatever/battery0/thinkpad/inhibit-charge-minutes for non-standard ones?
> + and the kernel can change the polling frequency based on power > saving state changes
Likewise for cached attributes (query hardware only if N jiffies passed since last querry, other return cached value). And that way, hardware query frequency is never higher than what userspace actually needs.
Shem - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |