From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755025Ab0IQW22 (ORCPT ); Fri, 17 Sep 2010 18:28:28 -0400 Received: from devils.ext.ti.com ([198.47.26.153]:54387 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754233Ab0IQW20 (ORCPT ); Fri, 17 Sep 2010 18:28:26 -0400 Message-ID: <4C93EB1A.7020203@ti.com> Date: Fri, 17 Sep 2010 17:26:34 -0500 From: Nishanth Menon User-Agent: Thunderbird 2.0.0.24 (X11/20100411) MIME-Version: 1.0 To: "Rafael J. Wysocki" CC: Mark Brown , linux-arm , lkml , Phil Carmody , linux-doc , "H. Peter Anvin" , Jesse Barnes , "Chikkature Rajashekar, Madhusudhan" , "Aguirre, Sergio" , Andi Kleen , linux-pm , Matthew Garrett , Len Brown , Eduardo Valentin , linux-omap , "Gopinath, Thara" , Linus Walleij , "Granados Dorado, Roberto" , "Martin K. Petersen" , Romit Dasgupta , Tero Kristo , Andrew Morton , "Premi, Sanjeev" Subject: Re: [linux-pm] [PATCH] opp: introduce library for device-specific OPPs References: <1284686973-13993-1-git-send-email-nm@ti.com> <20100917153643.GC29739@sirena.org.uk> <4C938EE2.1010307@ti.com> <201009180022.51011.rjw@sisk.pl> In-Reply-To: <201009180022.51011.rjw@sisk.pl> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Rafael J. Wysocki had written, on 09/17/2010 05:22 PM, the following: > On Friday, September 17, 2010, Nishanth Menon wrote: >> Mark Brown had written, on 09/17/2010 10:36 AM, the following: >>> On Thu, Sep 16, 2010 at 08:29:33PM -0500, Nishanth Menon wrote: >>> >>>> +struct opp_def { >>>> + unsigned long freq; >>>> + unsigned long u_volt; >>>> + >>>> + bool enabled; >>>> +}; >>> It might be clearer to use some term other than enabled in the code - >>> when reading I wasn't immediately sure if enabled meant that it was >>> available to be selected or if it was the active operating point. How >>> about 'allowed' (though I'm not 100% happy with that)? >> ;).. The opp is enabled or disabled if it is populated, it is implicit >> as being available but not enabled- how about active? this would change >> the opp_enable/disable functions to opp_activate, opp_deactivate.. > > Would that mean that "active" is the one currently in use? I like the idea Phil pointed out[1] on using "available" instead.. opp_enable and disable will make the OPP available or not. does this sound better? [1] http://marc.info/?l=linux-arm-kernel&m=128474217132058&w=2 -- Regards, Nishanth Menon