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]

Date:	Wed, 25 Mar 2009 10:03:29 -0700
From:	David Brownell <david-b@...bell.net>
To:	Adrian Hunter <adrian.hunter@...ia.com>
Cc:	Liam Girdwood <lrg@...mlogic.co.uk>,
	Mark Brown <broonie@...ena.org.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 Wednesday 25 March 2009, Adrian Hunter wrote:
> >> http://community.ti.com/forums/p/3777/14574.aspx
> >>
> >> So how do we do it?
> > 
> > I'd prefer seeing the reply from Ghandar to David's last question before
> > accepting this patch again. It's still not 100% clear from TI, things
> > seem a little bit muddled as to whether 3V will be guaranteed to work on
> > *all* shipped devices.
> 
> Ghandar has responded.  What would you like to do?

Update the patch to include a comment (by the table def)
that TI says they're revising the twl5030/tps659x0 specs
to support that 3.0V setting, then merge it.

(Umm, though I'd be sure to find out specifically which
selectors they're supporting that way, first...)

I don't think they'll be revising specs on chips they've
shipped already ... but this isn't likely to matter on
those older systems, anyway; example, the 3430 SDP uses
VAUX3, but at the always-supported 2.8V setting.



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