From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754052Ab0IIJiR (ORCPT ); Thu, 9 Sep 2010 05:38:17 -0400 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:45312 "EHLO opensource2.wolfsonmicro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750895Ab0IIJiP (ORCPT ); Thu, 9 Sep 2010 05:38:15 -0400 Date: Thu, 9 Sep 2010 10:38:10 +0100 From: Mark Brown To: Adrian Hunter Cc: Andrew Morton , Linus Walleij , "linux-kernel@vger.kernel.org" , Liam Girdwood , Tony Lindgren , Robert Jarzmik , Sundar Iyer , Daniel Mack , Pierre Ossman , Matt Fleming , David Brownell , Russell King , Eric Miao , Cliff Brake , "Lavinen Jarkko (Nokia-MS/Helsinki)" , "linux-mmc@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH] MMC: move regulator handling closer to core v3 Message-ID: <20100909093810.GA1988@rakim.wolfsonmicro.main> References: <1283677538-31121-1-git-send-email-linus.walleij@stericsson.com> <20100908155114.880463fc.akpm@linux-foundation.org> <4C887837.6060508@nokia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C887837.6060508@nokia.com> X-Cookie: Many suitcases look alike. User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 09, 2010 at 09:01:27AM +0300, Adrian Hunter wrote: > As an aside, I would like to enhance the regulator framework to > enable boards to hook their code directly into the regulator. What do you mean when you say that you would like boards to "hook directly into the regulator" - what do you want to be able to do? Is this the notifiers? Do you need more of them? > Arguably this is essential to allow pbias configuration (without > which the board may be damaged) so that regulator_enable/disable > can be used independently of the board, or for example to allow I can't parse this at all I'm afraid. Could you be more specific about what you mean by using enable and disable independantly of the board - clearly the consumer drivers are already able to be board independant? > the regulator core to turn the regulator on/off at initialisation. The regulator core already supports enabling or disabling regulators from the machine constraints which I *think* is what you're looking for but since I can't follow what you're saying above I'm not sure.