From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760620Ab0JIXAq (ORCPT ); Sat, 9 Oct 2010 19:00:46 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:59660 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756661Ab0JIXAo (ORCPT ); Sat, 9 Oct 2010 19:00:44 -0400 From: "Rafael J. Wysocki" To: Nishanth Menon , Kevin Hilman Subject: Re: [PATCH v7] power: introduce library for device-specific OPPs Date: Sun, 10 Oct 2010 00:59:20 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.36-rc7-rjw+; KDE/4.4.4; x86_64; ; ) Cc: "linux-pm" , lkml , "l-o" , "l-a" , Paul References: <[PATCH] power: introduce library for device-specific OPPs> <1286506969-20651-1-git-send-email-nm@ti.com> In-Reply-To: <1286506969-20651-1-git-send-email-nm@ti.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Message-Id: <201010100059.20964.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > Cc: Madhusudhan Chikkature Rajashekar > Cc: Phil Carmody > Cc: Roberto Granados Dorado > Cc: Santosh Shilimkar > Cc: Sergio Alberto Aguirre Rodriguez > Cc: Tero Kristo > Cc: Eduardo Valentin > Cc: Paul Walmsley > Cc: Sanjeev Premi > Cc: Thara Gopinath > Cc: Vishwanath BS > Cc: Linus Walleij > Cc: Mark Brown > Cc: Andrew Morton > Cc: Rafael J. Wysocki > Cc: Paul E. McKenney > > Signed-off-by: Nishanth Menon 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 Kevin, your sign-off here means you endorse the patch as the maintainer. Is that correct? Thanks, Rafael