From: eddie.cai.linux@gmail.com (Eddie Cai)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V1] ARM: dts: rockchip: correct regular setting for act8846
Date: Wed, 24 May 2017 16:48:06 +0800 [thread overview]
Message-ID: <1495615686-29949-1-git-send-email-eddie.cai.linux@gmail.com> (raw)
the previous setting of act8846 is just copy from firefly board. but
the reload board is a little different from firefly board. let's correct
it.
Signed-off-by: Eddie Cai <eddie.cai.linux@gmail.com>
---
arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi | 21 +++++++++++----------
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi b/arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi
index 8134966..4cfa109 100644
--- a/arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi
+++ b/arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi
@@ -179,6 +179,7 @@
regulator-name = "vccio_sd";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
+ regulator-boot-on;
};
vdd10_lcd: REG6 {
@@ -187,24 +188,23 @@
regulator-max-microvolt = <1000000>;
};
- vcca_18: REG7 {
- regulator-name = "vcca_18";
- regulator-min-microvolt = <1800000>;
- regulator-max-microvolt = <1800000>;
- regulator-always-on;
+ vcca_33: REG7 {
+ regulator-name = "vcca_33";
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
};
- vcca_33: REG8 {
- regulator-name = "vcca_33";
+ vcc_lan: REG8 {
+ regulator-name = "vcc_lan";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
- regulator-always-on;
};
- vcc_lan: REG9 {
- regulator-name = "vcca_lan";
+ vccio_pmu: REG9 {
+ regulator-name = "vccio_pmu";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
+ regulator-always-on;
};
vdd_10: REG10 {
@@ -218,6 +218,7 @@
regulator-name = "vcc_18";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
+ regulator-always-on;
};
vcc18_lcd: REG12 {
--
1.9.1
reply other threads:[~2017-05-24 8:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1495615686-29949-1-git-send-email-eddie.cai.linux@gmail.com \
--to=eddie.cai.linux@gmail.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).