From: Heiko Stuebner <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: amadeus@jmu.edu.cn, ziyao@disroot.org,
devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] rockchip: Add GPU support for RK3528
Date: Sat, 21 Jun 2025 20:44:12 +0200 [thread overview]
Message-ID: <2333578.IobQ9Gjlxr@phil> (raw)
In-Reply-To: <20250621090026.23293-1-amadeus@jmu.edu.cn>
Am Samstag, 21. Juni 2025, 11:00:26 Mitteleuropäische Sommerzeit schrieb Chukun Pan:
> Hi,
>
> > Applied, thanks!
> >
> > [2/3] arm64: dts: rockchip: Add GPU node for RK3528
> > commit: 6b88b8a640fa5d2169e0ce47b88dc30727fc1105
> > [3/3] arm64: dts: rockchip: Enable GPU on Radxa E20C
> > commit: 669080eb7f7c4720aa4e640a49f7490cd928cfcc
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?id=6b88b8a640fa5d2169e0ce47b88dc30727fc1105
>
> Should the gpu_opp_table node be above the pinctrl node?
yes it should. "o" before "p" :-) .
As tht commit was just from yesterday, I've amended it to move the
table to its correct position now.
Thanks for catching that.
Heiko
prev parent reply other threads:[~2025-06-21 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-18 22:54 [PATCH 0/3] rockchip: Add GPU support for RK3528 Jonas Karlman
2025-05-18 22:54 ` [PATCH 1/3] dt-bindings: gpu: mali-utgard: Add Rockchip RK3528 compatible Jonas Karlman
2025-05-19 16:10 ` Conor Dooley
2025-05-18 22:54 ` [PATCH 2/3] arm64: dts: rockchip: Add GPU node for RK3528 Jonas Karlman
2025-05-18 22:54 ` [PATCH 3/3] arm64: dts: rockchip: Enable GPU on Radxa E20C Jonas Karlman
2025-05-19 20:31 ` (subset) [PATCH 0/3] rockchip: Add GPU support for RK3528 Heiko Stuebner
2025-06-20 20:15 ` Heiko Stuebner
2025-06-21 9:00 ` Chukun Pan
2025-06-21 18:44 ` Heiko Stuebner [this message]
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=2333578.IobQ9Gjlxr@phil \
--to=heiko@sntech.de \
--cc=amadeus@jmu.edu.cn \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=ziyao@disroot.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