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 2/2] arm64: dts: rockchip: enable NPU on rk3588-jaguar
Date: Thu, 27 Nov 2025 14:28:58 +0100 [thread overview]
Message-ID: <3d9ef351-9eb9-41b1-beff-7a1deb73927b@cherry.de> (raw)
In-Reply-To: <20250812085213.1071106-2-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.
>
My apologies for the time it took me to review and test this.
I tested with aarch64 defconfig + DRM_ACCEL_ROCKET=m loosely following
the instructions from https://docs.mesa3d.org/teflon.html and the script
finishes, so I guess that means it works.
I have managed to get an Oops with another defconfig, but that is not
related to DT so not a blocker for merging this.
Thus:
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Tested-by: Quentin Schulz <quentin.schulz@cherry.de>
Note that I have the same remark about regulator-boot-on property in
vdd_npu_s0 I made[1] for Tiger here.
[1]
https://lore.kernel.org/linux-rockchip/d784230e-49f4-49e9-be4a-bc7c00020cfb@cherry.de/
Thanks!
Quentin
next prev parent reply other threads:[~2025-11-27 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 8:52 [PATCH 1/2] arm64: dts: rockchip: enable NPU on rk3588-tiger 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 [this message]
2025-08-22 15:16 ` [PATCH 1/2] arm64: dts: rockchip: enable NPU on rk3588-tiger Quentin Schulz
2025-11-28 10:32 ` 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=3d9ef351-9eb9-41b1-beff-7a1deb73927b@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®