public inbox for linux-kernel@vger.kernel.org
 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] ARM: dts: add dtsi for palmas
Date: Fri, 07 Jun 2013 13:56:05 -0600	[thread overview]
Message-ID: <51B23AD5.8060006@wwwdotorg.org> (raw)
In-Reply-To: <1370604504-32310-1-git-send-email-j-keerthy@ti.com>

On 06/07/2013 05:28 AM, J Keerthy wrote:
> Adds palmas mfd and palmas regulator nodes. This is
> based on the patch series:
> 
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg89957.html
> 
> The device tree nodes are based on:
> https://lkml.org/lkml/2013/6/6/25

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

> +&palmas {

Hmmm. That (i.e. requiring the board file to declare the node, then
setting up all the content by later including this file) is an
interesting approach. I guess it's reasonable. The one issue is that it
makes it a little harder for the board file to override any of the
properties in this file., although it certainly is possible by including
those overrides after the include.

Irrespective of that, some comments on this:

> +	palmas_pmic {

> +		ti,ldo6-vibrator;

For example, what if the board doesn't want to have the property set?

> +
> +		regulators {
> +			smps123_reg: smps123 {
> +				regulator-name = "smps123";
> +				regulator-min-microvolt = < 600000>;
> +				regulator-max-microvolt = <1500000>;

Or what if the board wants to limit the voltage range of this regulator
due to what it's used for on the board.

> +				regulator-always-on;
> +				regulator-boot-on;

And those two properties are almost certainly board-specific policy.


  parent reply	other threads:[~2013-06-07 19:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 11:28 [PATCH] ARM: dts: add dtsi for palmas J Keerthy
2013-06-07 12:27 ` Benoit Cousson
2013-06-07 12:32   ` J, KEERTHY
2013-06-07 19:22   ` Stephen Warren
2013-06-07 19:56 ` Stephen Warren [this message]
2013-06-10  4:03   ` J, KEERTHY
2013-06-10  8:04     ` Lee Jones
2013-06-10  9:29     ` Benoit Cousson
2013-06-10 10:17       ` J, KEERTHY
2013-06-10 16:21       ` Stephen Warren
2013-06-10 16:22     ` Stephen Warren

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=51B23AD5.8060006@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