The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: J Keerthy <j-keerthy@ti.com>
Cc: b-cousson@ti.com, devicetree-discuss@lists.ozlabs.org,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
	ldewangan@nvidia.com, grant.likely@secretlab.ca,
	swarren@nvidia.com, sameo@linux.intel.com, gg@slimlogic.co.uk,
	lee.jones@linaro.org
Subject: Re: [PATCH v2 1/2] ARM: dts: add dtsi for palmas
Date: Mon, 10 Jun 2013 10:29:18 -0600	[thread overview]
Message-ID: <51B5FEDE.5070900@wwwdotorg.org> (raw)
In-Reply-To: <1370855059-5342-2-git-send-email-j-keerthy@ti.com>

On 06/10/2013 03:04 AM, J Keerthy wrote:
> Adds palmas mfd and palmas regulator nodes.

Nits:

Well, you're really adding files that provide the nodes, not the nodes
themselves.

Palmas and MFD should be correctly capitalized.

> diff --git a/arch/arm/boot/dts/palmas.dtsi b/arch/arm/boot/dts/palmas.dtsi

> +&palmas {
...
> +	palmas_pmic {
...
> +		ti,ldo6-vibrator;

Isn't that board-specific? I don't know the HW well enough to say, but I
assume that since there's a property, the whole point must be that some
boards want it set and some don't.

> +		regulators {
> +			smps123_reg: smps123 {
> +				regulator-name = "smps123";
> +			};

So the node labels here duplicate those in omap5-uevm.dts in patch 2/2.
While dtc allows this, I don't think there's much point duplicating the
labels. I'd tend to only put the labels in omap5-uevm.dts and not put
them here. That will completely avoid the possibility of the labels in
this file from conflicting with any other labels in any top-level
board.dts file.

I also wonder if this file is actually terribly useful. The only thing
that this file provides is the regulator-name property. It seems simpler
just to put that into each board.dts file. The added advantage of doing
that, is that if a board doesn't use a particular regulator, the node
won't appear, and the regulator won't get registered.

  parent reply	other threads:[~2013-06-10 16:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10  9:04 [PATCH v2 0/2] ARM: dts: Add palmas dtsi J Keerthy
2013-06-10  9:04 ` [PATCH v2 1/2] ARM: dts: add dtsi for palmas J Keerthy
2013-06-10  9:25   ` Laxman Dewangan
2013-06-10  9:24     ` J, KEERTHY
2013-06-10 16:29   ` Stephen Warren [this message]
2013-06-11  4:10     ` J, KEERTHY
2013-06-10  9:04 ` [PATCH v2 2/2] ARM: dts: OMAP5: add palmas node and omap specific palmas regulator properties J Keerthy
2013-06-10 10:05   ` Lee Jones
2013-06-10 10:16     ` J, KEERTHY

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=51B5FEDE.5070900@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=gg@slimlogic.co.uk \
    --cc=grant.likely@secretlab.ca \
    --cc=j-keerthy@ti.com \
    --cc=ldewangan@nvidia.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=swarren@nvidia.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