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-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201010100059.20964.rjw@sisk.pl>
Date:	Sun, 10 Oct 2010 00:59:20 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Nishanth Menon <nm@...com>,
	Kevin Hilman <khilman@...prootsystems.com>
Cc:	"linux-pm" <linux-pm@...ts.linux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>,
	"l-o" <linux-omap@...r.kernel.org>,
	"l-a" <linux-arm-kernel@...ts.infradead.org>,
	Paul <paulmck@...ux.vnet.ibm.com>
Subject: Re: [PATCH v7] power: introduce library for device-specific OPPs

On Friday, October 08, 2010, Nishanth Menon wrote:
> SoCs have a standard set of tuples consisting of frequency and
> voltage pairs that the device will support per voltage domain. These
> are called Operating Performance Points or OPPs. The actual
> definitions of OPP varies over silicon versions. For a specific domain,
> we can have a set of {frequency, voltage} pairs. As the kernel boots
> and more information is available, a default set of these are activated
> based on the precise nature of device. Further on operation, based on
> conditions prevailing in the system (such as temperature), some OPP
> availability may be temporarily controlled by the SoC frameworks.
> 
> To implement an OPP, some sort of power management support is necessary
> hence this library depends on CONFIG_PM.
> 
> Contributions include:
> Sanjeev Premi for the initial concept:
> 	http://patchwork.kernel.org/patch/50998/
> Kevin Hilman for converting original design to device-based
> Kevin Hilman and Paul Walmsey for cleaning up many of the function
> abstractions, improvements and data structure handling
> Romit Dasgupta for using enums instead of opp pointers
> Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
> cleanups.
> Linus Walleij for recommending this layer be made generic for usage
> in other architectures beyond OMAP and ARM.
> Mark Brown, Andrew Morton, Rafael J Wysocki, Paul E McKenney for valuable
> improvements.
> 
> Discussions and comments from:
> http://marc.info/?l=linux-omap&m=126033945313269&w=2
> http://marc.info/?l=linux-omap&m=125482970102327&w=2
> http://marc.info/?t=125809247500002&r=1&w=2
> http://marc.info/?l=linux-omap&m=126025973426007&w=2
> http://marc.info/?t=128152609200064&r=1&w=2
> http://marc.info/?t=128468723000002&r=1&w=2
> incorporated.
> 
> Cc: Benoit Cousson <b-cousson@...com>
> Cc: Madhusudhan Chikkature Rajashekar <madhu.cr@...com>
> Cc: Phil Carmody <ext-phil.2.carmody@...ia.com>
> Cc: Roberto Granados Dorado <x0095451@...com>
> Cc: Santosh Shilimkar <santosh.shilimkar@...com>
> Cc: Sergio Alberto Aguirre Rodriguez <saaguirre@...com>
> Cc: Tero Kristo <Tero.Kristo@...ia.com>
> Cc: Eduardo Valentin <eduardo.valentin@...ia.com>
> Cc: Paul Walmsley <paul@...an.com>
> Cc: Sanjeev Premi <premi@...com>
> Cc: Thara Gopinath <thara@...com>
> Cc: Vishwanath BS <vishwanath.bs@...com>
> Cc: Linus Walleij <linus.walleij@...ricsson.com>
> Cc: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> Cc: Andrew Morton <akpm@...ux-foundation.org>
> Cc: Rafael J. Wysocki <rjw@...k.pl>
> Cc: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> 
> Signed-off-by: Nishanth Menon <nm@...com>

OK

Your error messages are a bit inconsistent (e.g. some of them print the
error code while others don't), but I guess I can fix that up.

Still, to apply the patch I need a copyright notice for the doc too.

> Signed-off-by: Kevin Hilman <khilman@...prootsystems.com>

Kevin, your sign-off here means you endorse the patch as the maintainer.
Is that correct?

Thanks,
Rafael
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ