Date: Fri, 6 Mar 2009 22:18:43 +0000
From: Mark Brown <broonie@sirena.org.uk>
To: David Brownell <david-b@pacbell.net>
Cc: Adrian Hunter <adrian.hunter@nokia.com>, lrg@slimlogic.co.uk,
       LKML <linux-kernel@vger.kernel.org>,
       linux-omap Mailing List <linux-omap@vger.kernel.org>
Message-ID: <20090306221842.GB15728@sirena.org.uk>
References: <49B11EB0.30809@nokia.com> <200903061116.21544.david-b@pacbell.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200903061116.21544.david-b@pacbell.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [PATCH] regulator: twl4030 VAUX3 supports 3.0V
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 812
Lines: 17

On Fri, Mar 06, 2009 at 11:16:20AM -0800, David Brownell wrote:

> Do you really need 3.0V out of that regulator?  If so,
> then I'd rather see a patch exposing that CONFIG_*
> setting to enable all the unsupported/out-of-range
> values, rather than just selectively hacking those
> tables to permit some (but not all) of them to be used
> out-of-range.

Would it make sense to make this platform data so that if a given board
requires running the chip like this it can be enabled for those boards
but it's not something people might turn on because it seems useful?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/