From: Chris Morgan <macroalpha82@gmail.com>
To: devicetree@vger.kernel.org
Cc: linux-rockchip@lists.infradead.org, lee.jones@linaro.org,
robh+dt@kernel.org, heiko@sntech.de, strit@manjaro.org,
mbrugger@suse.com, arnaud.ferraris@collabora.com,
knaerzche@gmail.com, zyw@rock-chips.com,
zhangqing@rock-chips.com, Chris Morgan <macromorgan@hotmail.com>,
Robin Murphy <robin.murphy@arm.com>
Subject: [PATCH 1/4 v5] arm64: dts: rockchip: Remove vcc13 and vcc14 for rk808
Date: Thu, 3 Mar 2022 14:39:55 -0600 [thread overview]
Message-ID: <20220303203958.4904-2-macroalpha82@gmail.com> (raw)
In-Reply-To: <20220303203958.4904-1-macroalpha82@gmail.com>
From: Chris Morgan <macromorgan@hotmail.com>
The Rockchip rk808 Power Management IC does not have a vcc13 or a
vcc14. The schematics for at least the Pinebook Pro suggest this is
actually vcc1 and vcc2, and may be an artifact from the reference
design schematic).
Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
---
arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts | 2 --
arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi | 2 --
2 files changed, 4 deletions(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts b/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts
index c2f021a1a18f..20f71317d7ab 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts
@@ -472,8 +472,6 @@ rk808: pmic@1b {
vcc10-supply = <&vcc_sysin>;
vcc11-supply = <&vcc_sysin>;
vcc12-supply = <&vcc3v3_sys>;
- vcc13-supply = <&vcc_sysin>;
- vcc14-supply = <&vcc_sysin>;
regulators {
/* rk3399 center logic supply */
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi
index d1aaf8e83391..0e45cc2d195b 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi
@@ -310,8 +310,6 @@ rk808: pmic@1b {
vcc10-supply = <&vcc3v3_sys>;
vcc11-supply = <&vcc3v3_sys>;
vcc12-supply = <&vcc3v3_sys>;
- vcc13-supply = <&vcc3v3_sys>;
- vcc14-supply = <&vcc3v3_sys>;
vddio-supply = <&vcc_3v0>;
regulators {
--
2.25.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2022-03-03 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 20:39 [PATCH 0/4 v5] rk808: Convert bindings to yaml Chris Morgan
2022-03-03 20:39 ` Chris Morgan [this message]
2022-03-03 20:39 ` [PATCH 2/4 v5] dts: rockchip: Add #clock-cells value for rk805 Chris Morgan
2022-03-03 20:39 ` [PATCH 3/4 v5] dts: rockchip: Update regulator name for PX3 Chris Morgan
2022-03-04 13:47 ` Robin Murphy
2022-03-03 20:39 ` [PATCH 4/4 v5] dt-bindings: mfd: rk808: Convert bindings to yaml Chris Morgan
2022-03-04 2:56 ` Rob Herring
2022-03-05 17:35 ` (subset) [PATCH 0/4 v5] " Heiko Stuebner
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=20220303203958.4904-2-macroalpha82@gmail.com \
--to=macroalpha82@gmail.com \
--cc=arnaud.ferraris@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=knaerzche@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macromorgan@hotmail.com \
--cc=mbrugger@suse.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=strit@manjaro.org \
--cc=zhangqing@rock-chips.com \
--cc=zyw@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).