mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	kernel@collabora.com
Subject: Re: [PATCH 2/5] arm64: dts: rockchip: Enable NPU on RK3588 EVB1
Date: Sun, 8 Nov 2026 10:03:05 +0800	[thread overview]
Message-ID: <f5edf258-4b6d-416a-9b27-efa47be8d91a@rock-chips.com> (raw)
In-Reply-To: <20261106-rk3588-evb1-dt-updates-v1-2-bdbe16223589@collabora.com>

On 11/7/2026 5:57 AM, Sebastian Reichel wrote:
> Also enable the NPU on the RK3588 EVB1, which is very similar to
> the QuartzPro64.
> 
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> ---

I remember there was already a similar patch before?
Maybe I got something wrong.

Reviewed-by: Chaoyi Chen <chaoyi.chen@rock-chips.com>

>  arch/arm64/boot/dts/rockchip/rk3588-evb1-v10.dts | 34 ++++++++++++++++++++++++
>  1 file changed, 34 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-evb1-v10.dts b/arch/arm64/boot/dts/rockchip/rk3588-evb1-v10.dts
> index 87e624d1e094..6476d9e3be6f 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588-evb1-v10.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-evb1-v10.dts
> @@ -578,6 +578,10 @@ &pd_gpu {
>  	domain-supply = <&vdd_gpu_s0>;
>  };
>  
> +&pd_npu {
> +	domain-supply = <&vdd_npu_s0>;
> +};
> +
>  &pd_rkvdec0 {
>  	domain-supply = <&vdd_vdenc_s0>;
>  };
> @@ -703,6 +707,36 @@ &pwm2 {
>  	status = "okay";
>  };
>  
> +&rknn_core_0 {
> +	npu-supply = <&vdd_npu_s0>;
> +	sram-supply = <&vdd_npu_mem_s0>;
> +	status = "okay";
> +};
> +
> +&rknn_core_1 {
> +	npu-supply = <&vdd_npu_s0>;
> +	sram-supply = <&vdd_npu_mem_s0>;
> +	status = "okay";
> +};
> +
> +&rknn_core_2 {
> +	npu-supply = <&vdd_npu_s0>;
> +	sram-supply = <&vdd_npu_mem_s0>;
> +	status = "okay";
> +};
> +
> +&rknn_mmu_0 {
> +	status = "okay";
> +};
> +
> +&rknn_mmu_1 {
> +	status = "okay";
> +};
> +
> +&rknn_mmu_2 {
> +	status = "okay";
> +};
> +
>  &saradc {
>  	vref-supply = <&vcc_1v8_s0>;
>  	status = "okay";
> 

-- 
Best, 
Chaoyi


  reply	other threads:[~2026-11-08  2:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 21:57 [PATCH 0/5] arm64: dts: rockchip: Enable more features " Sebastian Reichel
2026-11-06 21:57 ` [PATCH 1/5] arm64: dts: rockchip: Add missing PCIe wake pinmux " Sebastian Reichel
2026-11-06 21:57 ` [PATCH 2/5] arm64: dts: rockchip: Enable NPU " Sebastian Reichel
2026-11-08  2:03   ` Chaoyi Chen [this message]
2026-11-06 21:57 ` [PATCH 3/5] arm64: dts: rockchip: Enable HDMI sound " Sebastian Reichel
2026-11-06 21:57 ` [PATCH 4/5] arm64: dts: rockchip: Add DSI panel to " Sebastian Reichel
2026-11-06 21:57 ` [PATCH 5/5] arm64: dts: rockchip: Add Bluetooth " Sebastian Reichel

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=f5edf258-4b6d-416a-9b27-efa47be8d91a@rock-chips.com \
    --to=chaoyi.chen@rock-chips.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --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 \
    --cc=sebastian.reichel@collabora.com \
    /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®