From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "olof@lixom.net" <olof@lixom.net>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Stephen Warren <swarren@nvidia.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: dt: tegra: cardhu: register core regulator tps65911
Date: Sat, 9 Jun 2012 00:52:03 +0530 [thread overview]
Message-ID: <4FD250DB.2090207@nvidia.com> (raw)
In-Reply-To: <4FC916AC.4060804@wwwdotorg.org>
On Saturday 02 June 2012 12:53 AM, Stephen Warren wrote:
>
> We could either augment struct of_regulator_match with an integer ID
> field for each regulator (which would perhaps make it slightly painful
> to write the nodes and keep the IDs matched up), or add a new property
> to each regulator provider node e.g. regulator-id which contained the
> name that the regulator driver knows the regulator as (which would match
> struct of_regulator_match.name), since the existing regulator-name
> property is used for semantically different purposes.
>
> That would result in:
>
>> tps65911: tps65911@2d {
>> compatible = "ti,tps65911";
>> reg =<0x2d>;
>>
>> #gpio-cells =<2>;
>> gpio-controller;
>>
>> regulators {
>> #address-cells =<1>;
>> #size-cells =<0>;
>>
>> vdd1_reg: regulator@0 {
>> reg =<0>;
>> regulator-id = "vdd1"; /* Internal name */
>> regulator-name = "vdd_1v2_gen"; /* Signal on schematic */
> ...
>> };
>>
>> vdd2_reg: regulator@1 {
>> reg =<1>;
>> regulator-id = "vdd2";
>> regulator-name = "vdd_1v5_gen";
> ...
So is it fine to go on the above binding?
In this case we need to find the match_regulator based on regulator-id
rather than by name.
next prev parent reply other threads:[~2012-06-08 19:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 13:05 [PATCH 1/2] ARM: tegra: config: enable TPS65910 drivers Laxman Dewangan
2012-05-22 13:05 ` [PATCH 2/2] ARM: dt: tegra: cardhu: register core regulator tps65911 Laxman Dewangan
2012-05-22 16:40 ` Stephen Warren
2012-05-22 17:09 ` Laxman Dewangan
2012-05-22 17:19 ` Stephen Warren
2012-05-22 17:56 ` Laxman Dewangan
2012-05-22 18:27 ` Stephen Warren
2012-05-22 18:42 ` Laxman Dewangan
2012-06-01 19:23 ` Stephen Warren
2012-06-01 20:40 ` Mark Brown
2012-06-01 20:44 ` Stephen Warren
2012-06-01 21:04 ` Mark Brown
2012-06-02 21:19 ` Olof Johansson
2012-06-03 2:45 ` Rob Herring
2012-06-03 12:05 ` Mark Brown
[not found] ` <4FCB8CA9.40602@firmworks.com>
2012-06-03 18:37 ` Mark Brown
2012-06-03 11:55 ` Mark Brown
2012-06-08 19:22 ` Laxman Dewangan [this message]
2012-06-09 3:06 ` Mark Brown
2012-06-09 4:24 ` Stephen Warren
2012-06-11 2:57 ` Mark Brown
2012-06-11 15:56 ` Stephen Warren
2012-06-11 16:20 ` 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=4FD250DB.2090207@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
/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).