On Thu, 2006-09-14 at 04:22, Matthew Locke wrote:
> Unfortunately, there are two efforts underway that makes this confusing
> and I think require a bit more than the short summary requested. A one
> paragraph summary can't address the why and how. This email briefly
> describes the why and the differences.
>
> There are two main reasons for both these efforts:
> - existing power management interfaces do not enable the power
> management features on the latest SOC's used in embedded mobile
> devices
> - existing power management interfaces do not provide the API necessary
> to build power managers (userspace and/or kernel space) that optimize
> power consumption to level required by embedded mobile devices
So does it make sense to re-unify these two patch-sets
into one common, more general patch-set first? Might
it make sense to do so in small, incremental steps that
everyone can agree on as we go along?
For example, maybe the very first thing to do is define
some notion of general "operating point" that is a super-set
of the cpufreq definition. If we can define that structure
maybe we can progress towards introducing and using it.
Totally side-step the kernel-user level stuff for a bit...
Totally side-step the suspend/resume issues for a bit...
Thanks,
jdl
-
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]