From: Quentin Schulz <quentin.schulz@cherry.de>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: Re: [PATCH 1/2] arm64: dts: rockchip: enable NPU on rk3588-tiger
Date: Fri, 22 Aug 2025 17:16:37 +0200 [thread overview]
Message-ID: <d784230e-49f4-49e9-be4a-bc7c00020cfb@cherry.de> (raw)
In-Reply-To: <20250812085213.1071106-1-heiko@sntech.de>
Hi Heiko,
On 8/12/25 10:52 AM, Heiko Stuebner wrote:
> From: Heiko Stuebner <heiko.stuebner@cherry.de>
>
> Enable the NPU cores and their mmus and wire up the supply-regulator.
> The regulator itself was already defined, but it does not need to be
> always on - the npu can control it.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@cherry.de>
> ---
> .../arm64/boot/dts/rockchip/rk3588-tiger.dtsi | 35 ++++++++++++++++++-
> 1 file changed, 34 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-tiger.dtsi b/arch/arm64/boot/dts/rockchip/rk3588-tiger.dtsi
> index f4bebd25e938..9859f31d2894 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588-tiger.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-tiger.dtsi
> @@ -194,7 +194,6 @@ vdd_npu_s0: regulator@42 {
> reg = <0x42>;
> fcs,suspend-voltage-selector = <1>;
> regulator-name = "vdd_npu_s0";
> - regulator-always-on;
> regulator-boot-on;
I'm not sure we need this property?
The binding states:
"""
This property is intended to only be used for regulators where
software cannot read the state of the regulator.
"""
but the rk860 we use here can report its state if I read the driver
properly.
If that is correct the same "mistake" was done for other RK3588 boards
which enabled the NPU recently.
The diff makes sense compared to other RK3588 boards' recent NPU support
addition so I guess this is fine :)
I am currently unable to test this though but considering that this is
an IP within the SoC which only differs between different boards by its
regulator feeding the controller(s) and that this change looks in sync
with our hardware design, I guess we don't need to wait for me to be
able to test this :)
Same remarks for the next patch in the series.
Cheers,
Quentin
next prev parent reply other threads:[~2025-08-22 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 8:52 Heiko Stuebner
2025-08-12 8:52 ` [PATCH 2/2] arm64: dts: rockchip: enable NPU on rk3588-jaguar Heiko Stuebner
2025-11-27 13:28 ` Quentin Schulz
2025-08-22 15:16 ` Quentin Schulz [this message]
2025-11-28 10:32 ` [PATCH 1/2] arm64: dts: rockchip: enable NPU on rk3588-tiger Quentin Schulz
2026-01-06 18:52 ` Heiko Stuebner
2026-01-06 18:41 ` 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=d784230e-49f4-49e9-be4a-bc7c00020cfb@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=heiko.stuebner@cherry.de \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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
all inboxes | Powered by JetHome®