From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756197Ab2IMHTu (ORCPT ); Thu, 13 Sep 2012 03:19:50 -0400 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:45063 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752719Ab2IMHTj (ORCPT ); Thu, 13 Sep 2012 03:19:39 -0400 Date: Thu, 13 Sep 2012 15:19:30 +0800 From: Mark Brown To: Alex Courbot Cc: Tomi Valkeinen , Stephen Warren , Thierry Reding , Simon Glass , Grant Likely , Rob Herring , Anton Vorontsov , David Woodhouse , Arnd Bergmann , Leela Krishna Amudala , "linux-tegra@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-fbdev@vger.kernel.org" , "devicetree-discuss@lists.ozlabs.org" , "linux-pm@vger.kernel.org" , "linux-doc@vger.kernel.org" Subject: Re: [PATCH v6 0/4] Runtime Interpreted Power Sequences Message-ID: <20120913071928.GA20959@opensource.wolfsonmicro.com> References: <1347443867-18868-1-git-send-email-acourbot@nvidia.com> <1749811.4qrG1GZfBf@percival> <20120913062552.GB17869@opensource.wolfsonmicro.com> <4473898.CeAQBgUhKL@percival> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4473898.CeAQBgUhKL@percival> X-Cookie: Give him an evasive answer. User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 13, 2012 at 03:42:11PM +0900, Alex Courbot wrote: > On Thursday 13 September 2012 14:25:53 Mark Brown wrote: > > It would be sensible to make sure that the framework is done in such a > > way that drivers can use it - there will be drivers (perhaps not display > > ones) that have a known power sequence and which could benefit from the > > ability to use library code to implement it based on the user simply > > supplying named resources. > Not sure I understand what you mean, but things should be working this way > already - regulators and PWMs are acquired by name using the standard > regulator_get() and pwm_get() functions. GPIOs do not, AFAIK, have a way to be > referenced by name so their number is used instead. Right, but the sequencing for enabling them is currently open coded in each driver.