On Tue, 2007-07-24 at 16:02 -0700, [email protected] wrote:
>
> what requirements are needed? (I'm sure that there are others, but
> hopefully it's possible to avoid requirements like 'the clock speed
> for
> device A must be >X to allow device B to operate in mode Y')
I had an idea a while ago, might still be in the pm list archives, of
exposing constraints as opaque bitmaps. The bits have defined meaning
for a given bus, but are opaque to the core.
The devices however, provide tables indicating to the core their list of
power states (with names) and their requirements in term of parent
states (using such bitmasks).
Thus, the core can resolve the dependency requirements without having to
know about the actual meaning of the states of the various busses.
Ben.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
