linux-kernel - Re: [PATCH] regulator: twl4030 VAUX3 supports 3.0V

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090306221842.GB15728@sirena.org.uk>
Date:	Fri, 6 Mar 2009 22:18:43 +0000
From:	Mark Brown <broonie@...ena.org.uk>
To:	David Brownell <david-b@...bell.net>
Cc:	Adrian Hunter <adrian.hunter@...ia.com>, lrg@...mlogic.co.uk,
	LKML <linux-kernel@...r.kernel.org>,
	linux-omap Mailing List <linux-omap@...r.kernel.org>
Subject: Re: [PATCH] regulator: twl4030 VAUX3 supports 3.0V

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/