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: <1236599245.6781.86.camel@vega.slimlogic.co.uk>
Date:	Mon, 09 Mar 2009 11:47:25 +0000
From:	Liam Girdwood <lrg@...mlogic.co.uk>
To:	David Brownell <david-b@...bell.net>
Cc:	Mark Brown <broonie@...ena.org.uk>,
	Adrian Hunter <adrian.hunter@...ia.com>,
	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, 2009-03-06 at 14:48 -0800, David Brownell wrote:
> On Friday 06 March 2009, Mark Brown wrote:
> > 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?
> 
> Let's hear if it's actually needed, first.  :)
> 
> I coded those tables so that it would be easy to kick in the
> support for out-of-spec operation if it's really needed.  But
> so far we don't know that it's needed, and I'd rather it not
> be too easy to run like that.
> 

I've now reverted this patch. 

Liam

--
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/