linux-kernel - Re: [linux-pm] PowerOP vs OPpoint

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1158610046.6962.186.camel@cashmere.sps.mot.com>
Date:	Mon, 18 Sep 2006 15:07:27 -0500
From:	Jon Loeliger <jdl@...escale.com>
To:	Matthew Locke <matthew.a.locke@...cast.net>
Cc:	pm list <linux-pm@...ts.osdl.org>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] PowerOP vs OPpoint

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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/