From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "lrg@ti.com" <lrg@ti.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"rob@landley.net" <rob@landley.net>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] regulator: fixed: dt: support for input supply
Date: Wed, 4 Jul 2012 16:12:53 +0530 [thread overview]
Message-ID: <4FF41E2D.30104@nvidia.com> (raw)
In-Reply-To: <20120704102144.GE4111@opensource.wolfsonmicro.com>
On Wednesday 04 July 2012 03:51 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Wed, Jul 04, 2012 at 12:32:08PM +0530, Laxman Dewangan wrote:
>
>> In non-DT, the input supply is passed with the regulator_init_data
>> through the fixed voltage config and it is filled in board files.
> No, this is a legacy way of doing things. All regulators should be
> moving to specifying the name in their descriptor except for supplies
> that are power roots (which are often fixed voltage regulators).
Then the input_supply should be set through the regulator init data
"init_data->supply_regulator" rather than the desc? If yes then also I
need to change the forthcoming patch for tps65910 and tps6586x to pass
the supply_regulator through init_data.
next prev parent reply other threads:[~2012-07-04 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 10:07 [PATCH 1/2] regulator: fixed: use devm_* for gpio request Laxman Dewangan
2012-07-02 10:07 ` [PATCH 2/2] regulator: fixed: dt: support for input supply Laxman Dewangan
2012-07-03 19:17 ` Mark Brown
2012-07-04 7:02 ` Laxman Dewangan
2012-07-04 10:21 ` Mark Brown
2012-07-04 10:42 ` Laxman Dewangan [this message]
[not found] ` <4FF41E2D.30104-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-07-04 10:58 ` Mark Brown
2012-07-02 17:29 ` [PATCH 1/2] regulator: fixed: use devm_* for gpio request Mark Brown
2012-07-03 8:48 ` 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=4FF41E2D.30104@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
/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;
as well as URLs for NNTP newsgroup(s).