From: "Heiko Stübner" <heiko@sntech.de>
To: Frank Wang <frank.wang@rock-chips.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, huangtao@rock-chips.com,
kever.yang@rock-chips.com, david.wu@rock-chips.com,
finley.xiao@rock-chips.com, wmc@rock-chips.com
Subject: Re: [PATCH 1/6] ARM: dts: rockchip: add regulator nodes for rk3229-evb
Date: Tue, 04 Jul 2017 10:34:05 +0200 [thread overview]
Message-ID: <8062361.VWy3dYvDhe@diego> (raw)
In-Reply-To: <1499155967-26090-2-git-send-email-frank.wang@rock-chips.com>
Hi Frank,
Am Dienstag, 4. Juli 2017, 16:12:42 CEST schrieb Frank Wang:
> This patch adds vcc_io, vdd_arm and vdd_log regulator nodes
> for rk3229-evb board.
>
> Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
> ---
> arch/arm/boot/dts/rk3229-evb.dts | 54
> ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+)
>
> diff --git a/arch/arm/boot/dts/rk3229-evb.dts
> b/arch/arm/boot/dts/rk3229-evb.dts index 82e8a53..8b10c64 100644
> --- a/arch/arm/boot/dts/rk3229-evb.dts
> +++ b/arch/arm/boot/dts/rk3229-evb.dts
> @@ -78,6 +78,52 @@
> regulator-always-on;
> regulator-boot-on;
> };
> +
> + vdd_arm: vdd-arm-regulator {
> + compatible = "pwm-regulator";
> + rockchip,pwm_id = <1>;
> + rockchip,pwm_voltage = <1100000>;
This doesn't look like a part of the mainline pwm-regulator binding
(both rockchip,* properties)
> + pwms = <&pwm1 0 25000 1>;
> + regulator-name = "vdd_arm";
> + regulator-min-microvolt = <950000>;
> + regulator-max-microvolt = <1400000>;
> + regulator-always-on;
> + regulator-boot-on;
> + };
please also add supplies for regulators. Information on supplies
should be easily extractable from the board schematics.
This not only results in a nice tree in debugfs (regulator/regulator_summary)
but also makes sure supplying regulators are not accidentially turned off.
(pwm-supply for pwm-regulators, vin-supply for fixed regulators)
> +
> + vdd_log: vdd-log-regulator {
> + compatible = "pwm-regulator";
> + rockchip,pwm_id = <2>;
> + rockchip,pwm_voltage = <1200000>;
> + pwms = <&pwm2 0 25000 1>;
> + regulator-name = "vdd_log";
> + regulator-min-microvolt = <1000000>;
> + regulator-max-microvolt = <1300000>;
> + regulator-always-on;
> + regulator-boot-on;
> + };
> +
> + regulators {
> + compatible = "simple-bus";
don't create a subnode/bus for regulators. Just add them
regularly. Take a look at all the other boards (like rk3399-firefly,
gru, veyron) for reference.
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + vccio_1v8_reg: regulator@0 {
Same here, no regulator@0 please, just name this one
vccio_1v8: vccio-1v8-regulator {
(removed _reg from phandle and changed node name)
> + compatible = "regulator-fixed";
> + regulator-name = "vccio_1v8";
> + regulator-min-microvolt = <1800000>;
> + regulator-max-microvolt = <1800000>;
> + regulator-always-on;
> + };
> +
> + vccio_3v3_reg: regulator@1 {
> + compatible = "regulator-fixed";
> + regulator-name = "vccio_3v3";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + regulator-always-on;
> + };
> + };
> };
Thanks
Heiko
next prev parent reply other threads:[~2017-07-04 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 8:12 [PATCH 0/6] add and enable some device nodes for rk3229-evb board Frank Wang
2017-07-04 8:12 ` [PATCH 1/6] ARM: dts: rockchip: add regulator nodes for rk3229-evb Frank Wang
2017-07-04 8:34 ` Heiko Stübner [this message]
2017-07-04 9:37 ` Frank Wang
2017-07-04 8:12 ` [PATCH 2/6] ARM: dts: rockchip: add cpu-supply property for cpu node of rk3229-evb Frank Wang
2017-07-04 8:12 ` [PATCH 3/6] ARM: dts: rockchip: enable io-domain for rk3229-evb Frank Wang
2017-07-04 8:12 ` [PATCH 4/6] ARM: dts: rockchip: enable eMMC " Frank Wang
2017-07-04 8:35 ` Heiko Stübner
2017-07-04 8:14 ` [PATCH 5/6] ARM: dts: rockchip: enable tsadc " Frank Wang
2017-07-04 8:15 ` [PATCH 6/6] ARM: dts: rockchip: add gpio power-key " Frank Wang
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=8062361.VWy3dYvDhe@diego \
--to=heiko@sntech.de \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=finley.xiao@rock-chips.com \
--cc=frank.wang@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wmc@rock-chips.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;
as well as URLs for NNTP newsgroup(s).