Messages in this thread | | | Date | Thu, 19 Apr 2001 12:09:34 -0700 (PDT) | From | Patrick Mochel <> | Subject | Re: Next gen PM interface |
| |
> > > > (1) Battery status, power status, UPS status polling. It > > > > should be possible for lots of processes to do this > > > > simultaneously. [That does not prohibit a single process > > > > querying the kernel and all the others querying it.] > > > > > > Solution. Have a bunch of procfs or dev nodes each giving info on a > > > particular power source, like now, but vaguely standardise the output. > > [...] > > > I can see at least two types of events - (forgive the lack of colorful > > terminology) passive and active. Passive events are simply providing > > status updates, much like the events described above. These are simply so > > some UI can notify the user of things like a low battery or detection of > > an AC adapter. These can be handled in much the same way as described > > above. > > No they can't. They only happen once. Battery status exists all the > time.
Yes they can. My point was they can be handled from userspace in the same way that battery status does - by doing a select on a file in /proc or /dev. Once in a while (or constantly) they get data from the kernel - battery status, AC change, etc - that can be then translated and displayed in the UI.
-pat
- 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/
| |