linux-kernel - PowerOP summary

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <330177f4f8f83d0d39034c8f05d4b1f7@nomadgs.com>
Date:	Thu, 14 Sep 2006 01:28:25 -0700
From:	Matthew Locke <matt@...adgs.com>
To:	Greg KH <greg@...ah.com>, pm list <linux-pm@...ts.osdl.org>
Cc:	kernel list <linux-kernel@...r.kernel.org>
Subject: PowerOP summary

As a result of some discussion during the Linux PM summit between 
myself, Todd Poynor, Dominik Brodowski, Mark Gross, Amit Kucheria and a 
few others,  Eugeny and I have been working on getting a power 
management interface called PowerOP accepted.   A good bit of 
discussion has occurred on linux-pm over the last couple months about 
PowerOP interfaces and why its needed.  Here is a short summary 
requested by Greg:

Summary
PowerOP is an interface to create and select operating points.  
Operating points are a collection of platform specific system 
parameters (ie not i/o devices) that affect power consumption.  These 
parameters include cpu frequency, voltages, clock sources and dividers 
and others.  PowerOP provides a platform independent interface to 
control these platform specific parameters.   This interface is a basic 
building block of a power management stack for advanced power 
management on embedded mobile devices.  For those familiar with 
cpufreq, it can be viewed as a redesign of the cpufreq_driver layer to 
be platform independent and enable more advanced governors and policies 
on hardware with lots of power parameters.

Developers
Matthew Locke and Eugeny Mints are the main guys behind PowerOP now but 
many have contributed to get to this point.

A few key points
- PowerOP does not replace cpufreq
- PowerOP authors and advocates are not suggesting to replace cpufreq
- PowerOP is required for doing power management on embedded mobile 
devices
- PowerOP patches are standalone and do not require integration with 
cpufreq or suspend/resume subsystems
- PowerOP does not break anything including existing userspace 
interface and centrino code.

We will resend the patches again for review and discussion.  Each patch 
contains more detailed description.

Matt and Eugeny

-
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/