From: Dragan Simic <dsimic@manjaro.org>
To: linux-rockchip@lists.infradead.org
Cc: heiko@sntech.de, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-kernel@vger.kernel.org,
didi.debian@cknow.org, jonas@kwiboo.se
Subject: [PATCH v3 0/2] Add and update GPU OPP voltage ranges in the RK356x SoC dtsi
Date: Sun, 30 Jun 2024 18:00:39 +0200 [thread overview]
Message-ID: <cover.1719763100.git.dsimic@manjaro.org> (raw)
The first patch in this series adds support for voltage ranges to the GPU
OPPs defined in the SoC dtsi for Rockchip RK356x, which is, for example,
useful for RK356x-based boards designed to use the same power supply for
the GPU and NPU portions of the SoC.
The second patch updates the values for the exact GPU OPP voltages and
the lower limits for the GPU OPP voltage ranges, so they match the most
conservative values (i.e. the highest per-OPP voltages) found in the
vendor kernel source. This is performed in a separate patch to allow
easier regression tracking, in the unlikely case that some issues are
discovered later, resulting from these voltage changes.
Changes in v3:
- Turned into a patch series by adding a second patch that updates
the exact GPU OPP voltages and the lower limits for the GPU OPP
voltage ranges so they match the most conservative values found
in the vendor kernel source [1]
Changes in v2:
- Dropped support for optional GPU OPP voltage ranges, which may
actually hide some misconfiguration issues in board dts files, [2]
but that will be covered by other debugging patches [3]
Link to v2: https://lore.kernel.org/linux-rockchip/bdb60f1f793166cd65f58ab7aea025347076019c.1719679068.git.dsimic@manjaro.org/T/#u
Link to v1: https://lore.kernel.org/linux-rockchip/446399362bd2dbeeaecd8351f68811165429749a.1719637113.git.dsimic@manjaro.org/T/#u
[1] https://lore.kernel.org/linux-rockchip/b8951ac4e29184fa35919c6ab85b8f87@manjaro.org/
[2] https://lore.kernel.org/linux-rockchip/f10d5a3c425c2c4312512c20bd35073c@manjaro.org/
[3] https://lore.kernel.org/linux-rockchip/36170f8485293b336106e92346478daa@manjaro.org/
Dragan Simic (2):
arm64: dts: rockchip: Add GPU OPP voltage ranges to RK356x SoC dtsi
arm64: dts: rockchip: Update GPU OPP voltages in RK356x SoC dtsi
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
next reply other threads:[~2024-06-30 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 16:00 Dragan Simic [this message]
2024-06-30 16:00 ` [PATCH v3 1/2] arm64: dts: rockchip: Add GPU OPP voltage ranges to RK356x SoC dtsi Dragan Simic
2024-06-30 16:00 ` [PATCH v3 2/2] arm64: dts: rockchip: Update GPU OPP voltages in " Dragan Simic
2024-07-04 18:01 ` [PATCH v3 0/2] Add and update GPU OPP voltage ranges in the " 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.1719763100.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=jonas@kwiboo.se \
--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).