From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: grant.likely@secretlab.ca, rob.herring@calxeda.com, lrg@ti.com,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH V2] regulator: dt: fix the name of regulator supply
Date: Sat, 19 May 2012 11:43:03 +0100 [thread overview]
Message-ID: <20120519104303.GQ4039@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1337369652-27094-1-git-send-email-ldewangan@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
On Sat, May 19, 2012 at 01:04:12AM +0530, Laxman Dewangan wrote:
> If there is any input supply for regulator then the name
> of supply need to provided by init_data->supply_regulator.
> In dt case, the input supply is searched by the <name>-supply
> and here it is require to fix the name so that correct device
> node can be identified at the time of regulator registration.
> Fixing the name for input supply as "regulator-supply".
No, supply_regulator is a legacy thing. Regulators should set
supply_name in their regulator_desc to tell the framework what name
the parent has, allowing these supplies to behave in the same way
as other supplies as far as the binding goes.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-19 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 19:34 [PATCH V2] regulator: dt: fix the name of regulator supply Laxman Dewangan
2012-05-19 10:43 ` Mark Brown [this message]
2012-05-19 12:38 ` Laxman Dewangan
2012-05-19 13:10 ` Mark Brown
2012-05-19 14:21 ` 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=20120519104303.GQ4039@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rob.herring@calxeda.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 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).