From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: broonie@opensource.wolfsonmicro.com, ccross@android.com,
olof@lixom.net, lrg@ti.com, thierry.reding@avionic-design.de,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-doc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
rob.herring@calxeda.com, grant.likely@secretlab.ca
Subject: Re: [PATCH 1/2] ARM: tegra: harmony: add regulator supply name and its input supply
Date: Mon, 23 Jul 2012 14:49:36 -0600 [thread overview]
Message-ID: <500DB8E0.1050100@wwwdotorg.org> (raw)
In-Reply-To: <1342187432-18668-2-git-send-email-ldewangan@nvidia.com>
On 07/13/2012 07:50 AM, Laxman Dewangan wrote:
> Name the regulator as per board schematics and adds its
> supply name info in regulator data.
> Add the always on fixed regulator to refer the battery supply.
>
> Use this fixed regulator for input supply of some of PMIC
> regulator
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
Note that this file might well be deleted within the 3.7 development
cycle, since we will presumably get to the point where when booting from
DT, the DT will set up the regulators, and we won't support non-DT
booting any more on Harmony. Still, that should merge without issues, so
I don't think this will be a problem.
next prev parent reply other threads:[~2012-07-23 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 13:50 [PATCH 0/2] regulator: tps6586x: support for " Laxman Dewangan
2012-07-13 13:50 ` [PATCH 1/2] ARM: tegra: harmony: add regulator supply name and its " Laxman Dewangan
2012-07-23 20:49 ` Stephen Warren [this message]
2012-07-13 13:50 ` [PATCH 2/2] regulator: tps6586x: add support for " Laxman Dewangan
2012-07-13 14:22 ` Mark Brown
2012-07-13 17:15 ` Laxman Dewangan
2012-07-15 21:21 ` Mark Brown
2012-07-23 20:54 ` Stephen Warren
2012-07-23 21:30 ` Mark Brown
2012-07-23 20:51 ` Stephen Warren
2012-07-23 21:29 ` Mark Brown
2012-07-24 4:29 ` Laxman Dewangan
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=500DB8E0.1050100@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=ccross@android.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@ti.com \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
--cc=thierry.reding@avionic-design.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome