From: Michael Saunders <mick.saunders@gmail.com>
To: devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, heiko@sntech.de,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Michael Saunders <mick.saunders@gmail.com>
Subject: [PATCH v2] arm64: dts: rockchip: rk3399-firefly: enable the mali GPU
Date: Mon, 7 Feb 2022 17:06:19 +0930 [thread overview]
Message-ID: <20220207073617.7386-1-mick.saunders@gmail.com> (raw)
The Firefly RK3399 device tree had the GPU status set to disabled as per
the default from the rk3399.dtsi. This patch sets the status in the
firefly dts to enable it for use. Tested successfully on a 2GB Firefly
RK3399 board.
Signed-off-by: Michael Saunders <mick.saunders@gmail.com>
---
This should correct the issues raised in the first patch. Thanks Krzysztof for your feedback and patience.
arch/arm64/boot/dts/rockchip/rk3399-firefly.dts | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts b/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
index c4dd2a6b4836..65d659d56041 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
@@ -298,6 +298,11 @@ &gmac {
status = "okay";
};
+&gpu {
+ mali-supply = <&vdd_gpu>;
+ status = "okay";
+};
+
&hdmi {
ddc-i2c-bus = <&i2c3>;
pinctrl-names = "default";
--
2.35.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-02-07 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 7:36 Michael Saunders [this message]
2022-02-08 16:59 ` [PATCH v2] arm64: dts: rockchip: rk3399-firefly: enable the mali GPU 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=20220207073617.7386-1-mick.saunders@gmail.com \
--to=mick.saunders@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.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).