From: Krzysztof Kozlowski <krzk@kernel.org>
To: MidG971 <midgy971@gmail.com>,
Tomeu Vizoso <tomeu@tomeuvizoso.net>,
Oded Gabbay <ogabbay@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] dt-bindings: npu: rockchip,rk3588-rknn-core: Add RK3568 support
Date: Fri, 29 May 2026 18:18:16 +0200 [thread overview]
Message-ID: <53c4249e-8d6c-4bf7-86ff-b8d02117338a@kernel.org> (raw)
In-Reply-To: <20260529155824.3099831-3-midgy971@gmail.com>
On 29/05/2026 17:58, MidG971 wrote:
> From: Midgy BALON <midgy971@gmail.com>
>
> Add rockchip,rk3568-rknn-core to the compatible enum, document the
> new rockchip,pmu phandle that RK3568 needs for the NPU NOC bus de-idle
> sequence, and make sram-supply only required on RK3588 (RK3568 has no
> NPU SRAM rail).
>
> The driver supports both RK3568 and RK3588 RKNN cores; the binding now
> documents both. The rockchip,pmu phandle is consumed by the driver to
> issue PMU register writes (BUS_IDLE_SFTCON0, NOC_AUTO_CON0,
You need to start explaining the hardware, not drivers.
> PWR_GATE_SFTCON, BUS_IDLE_ST) on RK3568 only.
>
> Signed-off-by: Midgy BALON <midgy971@gmail.com>
> ---
> .../npu/rockchip,rk3588-rknn-core.yaml | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/npu/rockchip,rk3588-rknn-core.yaml b/Documentation/devicetree/bindings/npu/rockchip,rk3588-rknn-core.yaml
> index caca2a490..6582a0c5c 100644
> --- a/Documentation/devicetree/bindings/npu/rockchip,rk3588-rknn-core.yaml
> +++ b/Documentation/devicetree/bindings/npu/rockchip,rk3588-rknn-core.yaml
> @@ -21,6 +21,7 @@ properties:
>
> compatible:
> enum:
> + - rockchip,rk3568-rknn-core
> - rockchip,rk3588-rknn-core
>
> reg:
> @@ -50,6 +51,13 @@ properties:
>
> npu-supply: true
>
> + rockchip,pmu:
> + : /schemas/types.yaml#/definitions/phandle
I don't think you tested this.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-29 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 15:58 [PATCH v2 0/4] accel: rocket: Add RK3568 NPU support MidG971
2026-05-29 15:58 ` [PATCH v2 1/4] accel: rocket: Add support for Rockchip RK3568 MidG971
2026-05-29 18:19 ` Heiko Stuebner
2026-05-29 15:58 ` [PATCH v2 2/4] dt-bindings: npu: rockchip,rk3588-rknn-core: Add RK3568 support MidG971
2026-05-29 16:18 ` Krzysztof Kozlowski [this message]
2026-05-29 15:58 ` [PATCH v2 3/4] arm64: dts: rockchip: rk356x: Add NPU and its IOMMU MidG971
2026-05-29 15:58 ` [PATCH v2 4/4] arm64: dts: rockchip: rk3568-rock-3b: Enable NPU MidG971
2026-05-29 16:17 ` [PATCH v2 0/4] accel: rocket: Add RK3568 NPU support Krzysztof Kozlowski
2026-05-29 18:04 ` 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=53c4249e-8d6c-4bf7-86ff-b8d02117338a@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.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=midgy971@gmail.com \
--cc=ogabbay@kernel.org \
--cc=robh@kernel.org \
--cc=tomeu@tomeuvizoso.net \
/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