devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	"lrg@ti.com" <lrg@ti.com>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH V2] regulator: dt: fix the name of regulator supply
Date: Sat, 19 May 2012 19:51:16 +0530	[thread overview]
Message-ID: <4FB7AC5C.9060609@nvidia.com> (raw)
In-Reply-To: <20120519131019.GS4039@opensource.wolfsonmicro.com>

On Saturday 19 May 2012 06:40 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Sat, May 19, 2012 at 06:08:28PM +0530, Laxman Dewangan wrote:
>
>> The descriptor is set on the regulator driver and hence it need to
>> be parse this in the regulator driver.
>> We need to set the name regulator_desc->supply_name and hence it
>> needs to be in dt binding documentation of that device/regulators.
>> Is this what you recommend?
> I'm sorry, I still can't understand what you're trying to say here
> especially the first sentance.  Listing the name of the supply in the
> binding documentation doesn't seem like a bad idea if that's what you're
> trying to say.

Sorry for not explaining this in well.
In dts file for regulator, I want to specify the supply name same as the 
regulator name i.e.

more generic

my_reg1: abc {
:::::::::::
};

my_reg2: xyz {
::::::::::::::;
  xyz-supply = <&my_reg1>;
};


other way:
my_regname: <name> {
:::::::::;
<name>-supply = <&supply_reg>
};


This will be parsed in regulator driver file, not in core files.


-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------

      reply	other threads:[~2012-05-19 14:21 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
2012-05-19 12:38   ` Laxman Dewangan
2012-05-19 13:10     ` Mark Brown
2012-05-19 14:21       ` Laxman Dewangan [this message]

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=4FB7AC5C.9060609@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=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).