From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Stephen Warren <swarren@nvidia.com>,
"olof@lixom.net" <olof@lixom.net>,
"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>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 2/2] ARM: dt: tegra: cardhu: register core regulator tps65911
Date: Wed, 23 May 2012 00:12:14 +0530 [thread overview]
Message-ID: <4FBBDE06.5080806@nvidia.com> (raw)
In-Reply-To: <4FBBDA97.6000006@wwwdotorg.org>
On Tuesday 22 May 2012 11:57 PM, Stephen Warren wrote:
> On 05/22/2012 11:56 AM, Laxman Dewangan wrote:
>> On Tuesday 22 May 2012 10:49 PM, Stephen Warren wrote:
>>> On 05/22/2012 11:09 AM, Laxman Dewangan wrote:
>>>> On Tuesday 22 May 2012 10:10 PM, Stephen Warren wrote:
>>>>> On 05/22/2012 07:05 AM, Laxman Dewangan wrote:
>>>>>> Add device info for the PMIC device tps65911 in tegra-cardhu
>>>>>> dts file. This device supports the multiple regulator rails,
>>>>>> gpio, interrupts.
> ...
>>>>> Nitpicky, but the labels might be more logical as reg_vdd1 rather than
>>>>> vdd1_reg, but not a big deal.
>>>>>
>>>>> So, please replace the line above with:
>>>>>
>>>>> reg_vdd1: regulator@0 {
>>>>> reg =<0>;
>>>> Why do we really require the reg at all?
>>>> I dont think any usage of doing this.
> Oh, perhaps you meant the reg property not "reg_" in the label name?
>
> It is required because the parent node has #address-cells and
> #size-cells and because the node name itself has a unit address ("@nnn").
>
But we can not put
reg_vdd1:regulator@0 {
::::::::::::::
}
due to their dt binding with their node names.
In this case still do we need reg=<0> and #address-cells and #size-cells?
next prev parent reply other threads:[~2012-05-22 18:47 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 [this message]
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
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=4FBBDE06.5080806@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
all inboxes | Powered by JetHome®