From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] ARM: dts: bcm590xx: add support for GPLDO and VBUS regulators
Date: Wed, 21 May 2014 10:29:13 +0100 [thread overview]
Message-ID: <20140521092913.GG6679@lee--X1> (raw)
In-Reply-To: <1398295293-11033-5-git-send-email-mporter@linaro.org>
> Adds additional nodes to support GPLDO1-6 and VBUS regulators which
> are now supported in the bcm590xx regulator driver.
>
> Signed-off-by: Matt Porter <mporter@linaro.org>
> ---
> arch/arm/boot/dts/bcm59056.dtsi | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
I'm not going to apply this with the rest of the set. It will have to
go in via your normal arch/arm route.
> diff --git a/arch/arm/boot/dts/bcm59056.dtsi b/arch/arm/boot/dts/bcm59056.dtsi
> index dfadaaa..066adfb 100644
> --- a/arch/arm/boot/dts/bcm59056.dtsi
> +++ b/arch/arm/boot/dts/bcm59056.dtsi
> @@ -70,5 +70,26 @@
>
> vsr_reg: vsr {
> };
> +
> + gpldo1_reg: gpldo1 {
> + };
What do these empty nodes do in any case?
Don't you at least need a status property in there or something?
> + gpldo2_reg: gpldo2 {
> + };
> +
> + gpldo3_reg: gpldo3 {
> + };
> +
> + gpldo4_reg: gpldo4 {
> + };
> +
> + gpldo5_reg: gpldo5 {
> + };
> +
> + gpldo6_reg: gpldo6 {
> + };
> +
> + vbus_reg: vbus {
> + };
> };
> };
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Matt Porter <mporter-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Devicetree List
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Tim Kryger <tim.kryger-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Markus Mayer
<markus.mayer-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux ARM Kernel List
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v2 4/4] ARM: dts: bcm590xx: add support for GPLDO and VBUS regulators
Date: Wed, 21 May 2014 10:29:13 +0100 [thread overview]
Message-ID: <20140521092913.GG6679@lee--X1> (raw)
In-Reply-To: <1398295293-11033-5-git-send-email-mporter-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> Adds additional nodes to support GPLDO1-6 and VBUS regulators which
> are now supported in the bcm590xx regulator driver.
>
> Signed-off-by: Matt Porter <mporter-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> ---
> arch/arm/boot/dts/bcm59056.dtsi | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
I'm not going to apply this with the rest of the set. It will have to
go in via your normal arch/arm route.
> diff --git a/arch/arm/boot/dts/bcm59056.dtsi b/arch/arm/boot/dts/bcm59056.dtsi
> index dfadaaa..066adfb 100644
> --- a/arch/arm/boot/dts/bcm59056.dtsi
> +++ b/arch/arm/boot/dts/bcm59056.dtsi
> @@ -70,5 +70,26 @@
>
> vsr_reg: vsr {
> };
> +
> + gpldo1_reg: gpldo1 {
> + };
What do these empty nodes do in any case?
Don't you at least need a status property in there or something?
> + gpldo2_reg: gpldo2 {
> + };
> +
> + gpldo3_reg: gpldo3 {
> + };
> +
> + gpldo4_reg: gpldo4 {
> + };
> +
> + gpldo5_reg: gpldo5 {
> + };
> +
> + gpldo6_reg: gpldo6 {
> + };
> +
> + vbus_reg: vbus {
> + };
> };
> };
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Matt Porter <mporter@linaro.org>
Cc: Devicetree List <devicetree@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Tim Kryger <tim.kryger@linaro.org>,
Markus Mayer <markus.mayer@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 4/4] ARM: dts: bcm590xx: add support for GPLDO and VBUS regulators
Date: Wed, 21 May 2014 10:29:13 +0100 [thread overview]
Message-ID: <20140521092913.GG6679@lee--X1> (raw)
In-Reply-To: <1398295293-11033-5-git-send-email-mporter@linaro.org>
> Adds additional nodes to support GPLDO1-6 and VBUS regulators which
> are now supported in the bcm590xx regulator driver.
>
> Signed-off-by: Matt Porter <mporter@linaro.org>
> ---
> arch/arm/boot/dts/bcm59056.dtsi | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
I'm not going to apply this with the rest of the set. It will have to
go in via your normal arch/arm route.
> diff --git a/arch/arm/boot/dts/bcm59056.dtsi b/arch/arm/boot/dts/bcm59056.dtsi
> index dfadaaa..066adfb 100644
> --- a/arch/arm/boot/dts/bcm59056.dtsi
> +++ b/arch/arm/boot/dts/bcm59056.dtsi
> @@ -70,5 +70,26 @@
>
> vsr_reg: vsr {
> };
> +
> + gpldo1_reg: gpldo1 {
> + };
What do these empty nodes do in any case?
Don't you at least need a status property in there or something?
> + gpldo2_reg: gpldo2 {
> + };
> +
> + gpldo3_reg: gpldo3 {
> + };
> +
> + gpldo4_reg: gpldo4 {
> + };
> +
> + gpldo5_reg: gpldo5 {
> + };
> +
> + gpldo6_reg: gpldo6 {
> + };
> +
> + vbus_reg: vbus {
> + };
> };
> };
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-05-21 9:29 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 23:21 [PATCH v2 0/4] Support additional regulators on BCM590xx Matt Porter
2014-04-23 23:21 ` Matt Porter
2014-04-23 23:21 ` Matt Porter
2014-04-23 23:21 ` [PATCH v2 1/4] mfd: bcm590xx: update binding with additional BCM59056 regulators Matt Porter
2014-04-23 23:21 ` Matt Porter
2014-04-23 23:21 ` [PATCH v2 2/4] mfd: bcm590xx: add support for secondary I2C slave address Matt Porter
2014-04-23 23:21 ` Matt Porter
2014-04-28 11:56 ` Lee Jones
2014-04-28 11:56 ` Lee Jones
2014-04-28 11:56 ` Lee Jones
2014-04-28 14:09 ` Matt Porter
2014-04-28 14:09 ` Matt Porter
2014-05-20 16:11 ` Lee Jones
2014-05-20 16:11 ` Lee Jones
2014-05-20 16:11 ` Lee Jones
2014-05-20 19:00 ` Mark Brown
2014-05-20 19:00 ` Mark Brown
2014-05-20 19:00 ` Mark Brown
2014-05-20 20:29 ` Matt Porter
2014-05-20 20:29 ` Matt Porter
2014-05-20 20:29 ` Matt Porter
2014-05-20 21:44 ` Mark Brown
2014-05-20 21:44 ` Mark Brown
2014-05-20 21:44 ` Mark Brown
2014-05-20 21:57 ` Matt Porter
2014-05-20 21:57 ` Matt Porter
2014-05-20 21:57 ` Matt Porter
2014-05-20 22:17 ` Mark Brown
2014-05-20 22:17 ` Mark Brown
2014-05-21 9:26 ` Lee Jones
2014-05-21 9:26 ` Lee Jones
2014-05-21 9:26 ` Lee Jones
2014-04-23 23:21 ` [PATCH v2 3/4] regulator: bcm590xx: add support for regulators on secondary I2C slave Matt Porter
2014-04-23 23:21 ` Matt Porter
2014-04-23 23:21 ` Matt Porter
2014-04-23 23:21 ` [PATCH v2 4/4] ARM: dts: bcm590xx: add support for GPLDO and VBUS regulators Matt Porter
2014-04-23 23:21 ` Matt Porter
2014-05-21 9:29 ` Lee Jones [this message]
2014-05-21 9:29 ` Lee Jones
2014-05-21 9:29 ` Lee Jones
2014-05-21 12:02 ` Matt Porter
2014-05-21 12:02 ` Matt Porter
2014-05-21 12:02 ` Matt Porter
2014-05-21 13:30 ` Lee Jones
2014-05-21 13:30 ` Lee Jones
2014-05-23 12:09 ` Matt Porter
2014-05-23 12:09 ` Matt Porter
2014-05-23 12:09 ` Matt Porter
2014-05-21 9:48 ` [GIT PULL] mfd: Second IB for Mark (regulator) Lee Jones
2014-05-21 9:48 ` Lee Jones
2014-05-21 23:18 ` Mark Brown
2014-05-21 23:18 ` Mark Brown
2014-05-21 23:18 ` 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=20140521092913.GG6679@lee--X1 \
--to=lee.jones@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.