From: Trevor Woerner <twoerner@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Katsuhiro Suzuki <katsuhiro@katsuster.net>,
Chen-Yu Tsai <wens@csie.org>, Cameron Nemo <cnemo@tutanota.com>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-arm-kernel@lists.infradead.org (moderated
list:ARM/Rockchip SoC support),
linux-rockchip@lists.infradead.org (open list:ARM/Rockchip SoC
support)
Subject: [PATCH 2/2] arm64: dts: rock64: add gpu regulator
Date: Sat, 16 Oct 2021 11:45:45 -0400 [thread overview]
Message-ID: <20211016154548.29555-2-twoerner@gmail.com> (raw)
In-Reply-To: <20211016154548.29555-1-twoerner@gmail.com>
Add a regulator for the GPU in order to properly make use of the newly added
operations-table.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
arch/arm64/boot/dts/rockchip/rk3328-rock64.dts | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
index 1b0f7e4551ea..e76673d5fdc5 100644
--- a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
@@ -133,6 +133,10 @@ &cpu3 {
cpu-supply = <&vdd_arm>;
};
+&gpu {
+ mali-supply = <&vdd_logic>;
+};
+
&emmc {
bus-width = <8>;
cap-mmc-highspeed;
--
2.30.0.rc0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-16 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 15:45 [PATCH 1/2] arm64: dts: rk3328: add gpu opp table Trevor Woerner
2021-10-16 15:45 ` Trevor Woerner [this message]
2021-10-16 20:45 ` Johan Jonker
2021-10-17 15:29 ` Trevor Woerner
2021-10-18 18:09 ` Robin Murphy
2021-10-18 16:49 ` Nicolas Frattaroli
2021-10-19 15:52 ` Alex Bee
2021-10-19 16:19 ` Nicolas Frattaroli
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=20211016154548.29555-2-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=cnemo@tutanota.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=katsuhiro@katsuster.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).