From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752896Ab0IQWxG (ORCPT ); Fri, 17 Sep 2010 18:53:06 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:40630 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751136Ab0IQWxE (ORCPT ); Fri, 17 Sep 2010 18:53:04 -0400 From: "Rafael J. Wysocki" To: Nishanth Menon Subject: Re: [linux-pm] [PATCH] opp: introduce library for device-specific OPPs Date: Sat, 18 Sep 2010 00:52:21 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.36-rc4-rjw+; KDE/4.4.4; x86_64; ; ) 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" References: <1284686973-13993-1-git-send-email-nm@ti.com> <201009180022.51011.rjw@sisk.pl> <4C93EB1A.7020203@ti.com> In-Reply-To: <4C93EB1A.7020203@ti.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201009180052.21574.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Saturday, September 18, 2010, Nishanth Menon wrote: > 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? Yes, it does. Rafael