From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "sameo@linux.intel.com" <sameo@linux.intel.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Stephen Warren <swarren@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH] regulator: tps6586x: add support for SYS rail
Date: Thu, 2 Aug 2012 17:21:38 +0530 [thread overview]
Message-ID: <501A69CA.2070507@nvidia.com> (raw)
In-Reply-To: <20120802114046.GK29157@opensource.wolfsonmicro.com>
On Thursday 02 August 2012 05:10 PM, Mark Brown wrote:
> On Thu, Aug 02, 2012 at 04:46:33PM +0530, Laxman Dewangan wrote:
>
>> +static const unsigned int tps6586x_sys_voltages[] = {
>> + 5000000,
>> +};
> Is the system rail actually regulated or is it just a nominal 5V?
> Normally it's just the raw, unregulated input switched in with FETs or
> whatever.
It is unregulated with FET.
The typical range (min-max) shows in data sheet
V(SYS) with respect to AGND1: 2.9V(min) 5.5V(max).
althoguh USB or AC have 4.30V(Min) 16.5V(max)
next prev parent reply other threads:[~2012-08-02 11:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 11:16 [PATCH] regulator: tps6586x: add support for SYS rail Laxman Dewangan
2012-08-02 11:16 ` Laxman Dewangan
2012-08-02 11:40 ` Mark Brown
2012-08-02 11:51 ` Laxman Dewangan [this message]
2012-08-02 16:10 ` Mark Brown
[not found] ` <1343906193-8309-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-02 16:44 ` Stephen Warren
2012-08-02 16:44 ` Stephen Warren
2012-08-03 6:09 ` Laxman Dewangan
2012-08-04 0:52 ` Mark Brown
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=501A69CA.2070507@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=sameo@linux.intel.com \
--cc=swarren@nvidia.com \
/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.