linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: am335x-boneblack: Add names for remaining regulators
Date: Mon, 8 Sep 2014 17:19:35 -0700	[thread overview]
Message-ID: <20140909001935.GD10785@atomide.com> (raw)
In-Reply-To: <1409951525-30035-1-git-send-email-broonie@kernel.org>

* Mark Brown <broonie@kernel.org> [140905 14:12]:
> Add regulator-name properties for the regulators that don't have them,
> allowing the kernel to display the name from the schematic rather than
> the name of the regulator on the PMIC in order to improve diagnostics.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>

Applying into omap-for-v3.18/dt thanks.

Tony

> ---
>  arch/arm/boot/dts/am335x-bone-common.dtsi | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/am335x-bone-common.dtsi b/arch/arm/boot/dts/am335x-bone-common.dtsi
> index bde1777b62be..fe983d204b2b 100644
> --- a/arch/arm/boot/dts/am335x-bone-common.dtsi
> +++ b/arch/arm/boot/dts/am335x-bone-common.dtsi
> @@ -227,6 +227,7 @@
>  &tps {
>  	regulators {
>  		dcdc1_reg: regulator at 0 {
> +			regulator-name = "vdds_dpr";
>  			regulator-always-on;
>  		};
>  
> @@ -249,18 +250,22 @@
>  		};
>  
>  		ldo1_reg: regulator at 3 {
> +			regulator-name = "vio,vrtc,vdds";
>  			regulator-always-on;
>  		};
>  
>  		ldo2_reg: regulator at 4 {
> +			regulator-name = "vdd_3v3aux";
>  			regulator-always-on;
>  		};
>  
>  		ldo3_reg: regulator at 5 {
> +			regulator-name = "vdd_1v8";
>  			regulator-always-on;
>  		};
>  
>  		ldo4_reg: regulator at 6 {
> +			regulator-name = "vdd_3v3a";
>  			regulator-always-on;
>  		};
>  	};
> -- 
> 2.1.0
> 

      reply	other threads:[~2014-09-09  0:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05 21:12 [PATCH] ARM: dts: am335x-boneblack: Add names for remaining regulators Mark Brown
2014-09-09  0:19 ` Tony Lindgren [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=20140909001935.GD10785@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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).