From: Adrian Hunter <adrian.hunter@nokia.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: David Brownell <david-b@pacbell.net>,
Mark Brown <broonie@sirena.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
linux-omap Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] regulator: twl4030 VAUX3 supports 3.0V
Date: Wed, 25 Mar 2009 10:28:07 +0200 [thread overview]
Message-ID: <49C9EB17.2020408@nokia.com> (raw)
In-Reply-To: <1237290190.6781.313.camel@vega.slimlogic.co.uk>
Liam Girdwood wrote:
> On Tue, 2009-03-17 at 09:36 +0200, Adrian Hunter wrote:
>> Liam Girdwood wrote:
>>> 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.
>> TI say we can use VAUX3 at 3V and expect no problems:
>>
>> 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?
next prev parent reply other threads:[~2009-03-25 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 13:01 [PATCH] regulator: twl4030 VAUX3 supports 3.0V Adrian Hunter
2009-03-06 18:23 ` Liam Girdwood
2009-03-06 19:16 ` David Brownell
2009-03-06 22:18 ` Mark Brown
2009-03-06 22:48 ` David Brownell
2009-03-09 11:47 ` Liam Girdwood
2009-03-17 7:36 ` Adrian Hunter
2009-03-17 11:43 ` Liam Girdwood
2009-03-25 8:28 ` Adrian Hunter [this message]
2009-03-25 17:03 ` David Brownell
2009-03-25 17:03 ` David Brownell
2009-03-26 14:21 ` Adrian Hunter
2009-03-31 10:43 ` Liam Girdwood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49C9EB17.2020408@nokia.com \
--to=adrian.hunter@nokia.com \
--cc=broonie@sirena.org.uk \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.