From: bcousson@baylibre.com (Benoit Cousson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap5: dts: split SMPS10 dt node
Date: Tue, 13 Aug 2013 15:21:19 +0200 [thread overview]
Message-ID: <520A32CF.1010701@baylibre.com> (raw)
In-Reply-To: <1376300221-15172-1-git-send-email-kishon@ti.com>
Hi Kishon,
On 12/08/2013 11:37, Kishon Vijay Abraham I wrote:
> SMPS10 has two outputs OUT1 and OUT2. Hence SMPS10 is modeled as
> two regulators. The dt node is split to reflect it.
Mmm, I'm curious. How is it supposed to work?
Do you have dedicated control on each output?
Otherwise, it should be seen as one output with two potential consumers.
Regards,
Benoit
>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> ---
> arch/arm/boot/dts/omap5-uevm.dts | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
> index 65d7b60..05b9b12 100644
> --- a/arch/arm/boot/dts/omap5-uevm.dts
> +++ b/arch/arm/boot/dts/omap5-uevm.dts
> @@ -334,9 +334,18 @@
> ti,smps-range = <0x80>;
> };
>
> - smps10_reg: smps10 {
> + smps10_out2_reg: smps10_out2 {
> /* VBUS_5V_OTG */
> - regulator-name = "smps10";
> + regulator-name = "smps10_out2";
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + regulator-always-on;
> + regulator-boot-on;
> + };
> +
> + smps10_out1_reg: smps10_out1 {
> + /* VBUS_5V_OTG */
> + regulator-name = "smps10_out1";
> regulator-min-microvolt = <5000000>;
> regulator-max-microvolt = <5000000>;
> regulator-always-on;
>
next prev parent reply other threads:[~2013-08-13 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 9:37 [PATCH] arm: omap5: dts: split SMPS10 dt node Kishon Vijay Abraham I
2013-08-13 13:21 ` Benoit Cousson [this message]
2013-08-13 14:45 ` Kishon Vijay Abraham I
2013-08-13 14:48 ` Benoit Cousson
2013-08-16 5:15 ` Kishon Vijay Abraham I
2013-08-16 8:54 ` Benoit Cousson
2013-08-16 10:21 ` Kishon Vijay Abraham I
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=520A32CF.1010701@baylibre.com \
--to=bcousson@baylibre.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).