From: Dragan Simic <dsimic@manjaro.org>
To: linux-rockchip@lists.infradead.org
Cc: heiko@sntech.de, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
didi.debian@cknow.org
Subject: [PATCH v2 0/3] Update, encapsulate and expand the RK356x SoC dtsi files
Date: Sat, 2 Nov 2024 04:08:58 +0100 [thread overview]
Message-ID: <cover.1730516702.git.dsimic@manjaro.org> (raw)
This series tackles the Rockchip RK356x SoC dtsi files in a few different
ways. First, it updates the lower and upper voltage limits and the exact
voltages for the Rockchip RK356x CPU OPPs, using the most conservative
per-OPP values for different SoC bins. This is rather similar to the
already performed adjustment of the GPU OPP voltages. [1]
Next, this series prepares the RK356x SoC dtsi files for per-variant OPPs,
with the RK3566T being the first new RK356x SoC variant to be introduced.
This follows the approach used for the RK3588 SoC variants. [2]
Lastly, this series introduces new SoC dtsi for the RK3566T variant, which
is capable of operating at the CPU and GPU OPPs/frequencies lower than the
"full-fat" RK3566 variant's. The RK3566T is found on some of the already
supported boards and rather importantly, this stops the CPU cores and the
GPU from being overclocked on these boards.
Changes in v2:
- Improved the wording of the patch 3/3 description, to make it more
clear which of the mentioned RK3566T-based SBCs are already supported
- Renumbered the references in patch 3/3, so their numbering follows
the order in which the references appear in the patch description
- Adjusted the patch generation options passed to git-format-patch(1),
to make the patch 2/3 a bit more readable, [3] and added a note about
the git-log(1) options to the description of patch 2/3
- No changes to the actual patches are introduced
Link to v1: https://lore.kernel.org/linux-rockchip/cover.1728752527.git.dsimic@manjaro.org/T/#u
[1] https://lore.kernel.org/linux-rockchip/cover.1719763100.git.dsimic@manjaro.org/T/#m786f0e0a45377d29aea826f05c95b5052a8bb3d9
[2] https://lore.kernel.org/all/9ffedc0e2ca7f167d9d795b2a8f43cb9f56a653b.1717923308.git.dsimic@manjaro.org/T/#u
[3] https://lore.kernel.org/linux-rockchip/D4ZZFL98AMFI.1TDPL2DJPSQ3D@cknow.org/
Dragan Simic (3):
arm64: dts: rockchip: Update CPU OPP voltages in RK356x SoC dtsi
arm64: dts: rockchip: Prepare RK356x SoC dtsi files for per-variant
OPPs
arm64: dts: rockchip: Add new SoC dtsi for the RK3566T variant
.../{rk3566.dtsi => rk3566-base.dtsi} | 2 +-
.../dts/rockchip/rk3566-radxa-zero-3.dtsi | 2 +-
.../boot/dts/rockchip/rk3566-rock-3c.dts | 2 +-
arch/arm64/boot/dts/rockchip/rk3566.dtsi | 142 +++++++++++++-----
arch/arm64/boot/dts/rockchip/rk3566t.dtsi | 90 +++++++++++
arch/arm64/boot/dts/rockchip/rk3568.dtsi | 113 +++++++++++++-
.../{rk356x.dtsi => rk356x-base.dtsi} | 81 ----------
7 files changed, 307 insertions(+), 125 deletions(-)
copy arch/arm64/boot/dts/rockchip/{rk3566.dtsi => rk3566-base.dtsi} (95%)
rewrite arch/arm64/boot/dts/rockchip/rk3566.dtsi (87%)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3566t.dtsi
rename arch/arm64/boot/dts/rockchip/{rk356x.dtsi => rk356x-base.dtsi} (96%)
next reply other threads:[~2024-11-02 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 3:08 Dragan Simic [this message]
2024-11-02 3:08 ` [PATCH v2 1/3] arm64: dts: rockchip: Update CPU OPP voltages in RK356x SoC dtsi Dragan Simic
2024-11-02 3:09 ` [PATCH v2 2/3] arm64: dts: rockchip: Prepare RK356x SoC dtsi files for per-variant OPPs Dragan Simic
2024-11-02 3:09 ` [PATCH v2 3/3] arm64: dts: rockchip: Add new SoC dtsi for the RK3566T variant Dragan Simic
2024-11-09 18:27 ` [PATCH v2 0/3] Update, encapsulate and expand the RK356x SoC dtsi files 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=cover.1730516702.git.dsimic@manjaro.org \
--to=dsimic@manjaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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).