From: sashiko-bot@kernel.org
To: "Dawid Olesinski" <dawidro@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 3/4] arm64: dts: rockchip: Add crypto node to rk356x-base
Date: Sun, 16 Aug 2026 19:48:36 +0000 [thread overview]
Message-ID: <20260816194836.C7D0B1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260816194112.552100-4-dawidro@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `crypto` device tree node is missing the `status = "disabled";` property, contradicting the commit message and enabling it by default on all boards.
--
--- Patch [3]: [PATCH v3 3/4] arm64: dts: rockchip: Add crypto node to rk356x-base ---
commit 452b9449e76bd94304ad239887547298226d6bf8
Author: Dawid Olesinski <dawidro@gmail.com>
arm64: dts: rockchip: Add crypto node to rk356x-base
This commit adds the device tree node for the V2 cryptographic hardware
accelerator on RK356x SoCs to the base dtsi file. The commit message notes
that the node is disabled by default and should be enabled by board files
that wish to use hardware crypto offload.
> diff --git a/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi b/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> --- a/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
[ ... ]
> @@ -1112,6 +1112,17 @@ sdhci: mmc@fe310000 {
> status = "disabled";
> };
>
> + crypto: crypto@fe380000 {
> + compatible = "rockchip,rk3568-crypto";
> + reg = <0x0 0xfe380000 0x0 0x2000>;
> + interrupts = <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cru CLK_CRYPTO_NS_CORE>, <&cru ACLK_CRYPTO_NS>,
> + <&cru HCLK_CRYPTO_NS>;
> + clock-names = "core", "aclk", "hclk";
> + resets = <&cru SRST_CRYPTO_NS_CORE>;
> + reset-names = "core";
> + };
[Severity: Medium]
Does this node need a status = "disabled"; property to match the commit
message?
The commit message states: "The node is disabled by default; board files
that wish to use hardware crypto offload must enable it."
Because device tree nodes default to "okay" when the status property is
omitted, the lack of status = "disabled" here will cause the cryptographic
offloader driver to automatically probe on all RK356x boards that include
rk356x-base.dtsi, rather than requiring board files to enable it.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260816194112.552100-1-dawidro@gmail.com?part=3
next prev parent reply other threads:[~2026-08-16 19:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 17:58 [PATCH v2 0/4] crypto: rockchip: Add RK356x/RK3588 cryptographic offloader Dawid Olesinski
2026-07-08 17:58 ` Dawid Olesinski
2026-07-08 17:58 ` [PATCH v2 1/4] dt-bindings: crypto: rockchip: Add RK356x/RK3588 crypto engine binding Dawid Olesinski
2026-07-08 17:58 ` Dawid Olesinski
2026-07-08 18:13 ` sashiko-bot
2026-07-08 23:53 ` Sebastian Reichel
2026-07-08 23:53 ` Sebastian Reichel
2026-07-08 17:58 ` [PATCH v2 2/4] crypto: rockchip: Add RK356x/RK3588 cryptographic offloader driver Dawid Olesinski
2026-07-08 17:58 ` Dawid Olesinski
2026-07-08 18:13 ` sashiko-bot
2026-07-08 17:58 ` [PATCH v2 3/4] arm64: dts: rockchip: Add crypto node to rk356x-base Dawid Olesinski
2026-07-08 17:58 ` Dawid Olesinski
2026-07-08 23:56 ` Sebastian Reichel
2026-07-08 23:56 ` Sebastian Reichel
2026-07-09 7:07 ` Heiko Stübner
2026-07-09 7:07 ` Heiko Stübner
2026-07-10 14:30 ` Dawid Olesinski
2026-07-10 14:30 ` Dawid Olesinski
2026-07-25 14:13 ` Diederik de Haas
2026-07-25 14:13 ` Diederik de Haas
2026-07-08 17:58 ` [PATCH v2 4/4] arm64: dts: rockchip: Add crypto node to rk3588-base Dawid Olesinski
2026-07-08 17:58 ` Dawid Olesinski
2026-08-03 10:42 ` [PATCH v2 0/4] crypto: rockchip: Add RK356x/RK3588 cryptographic offloader Diederik de Haas
2026-08-03 10:42 ` Diederik de Haas
2026-08-16 19:39 ` [PATCH v3 " Dawid Olesinski
2026-08-16 19:39 ` Dawid Olesinski
2026-08-16 19:39 ` [PATCH v3 1/4] dt-bindings: crypto: rockchip: Add RK356x/RK3588 crypto engine binding Dawid Olesinski
2026-08-16 19:39 ` Dawid Olesinski
2026-08-16 19:49 ` sashiko-bot
2026-08-16 19:39 ` [PATCH v3 2/4] crypto: rockchip: Add RK356x/RK3588 cryptographic offloader driver Dawid Olesinski
2026-08-16 19:39 ` Dawid Olesinski
2026-08-16 19:56 ` sashiko-bot
2026-08-16 19:39 ` [PATCH v3 3/4] arm64: dts: rockchip: Add crypto node to rk356x-base Dawid Olesinski
2026-08-16 19:39 ` Dawid Olesinski
2026-08-16 19:48 ` sashiko-bot [this message]
2026-08-16 19:39 ` [PATCH v3 4/4] arm64: dts: rockchip: Add crypto node to rk3588-base Dawid Olesinski
2026-08-16 19:39 ` Dawid Olesinski
2026-08-16 19:51 ` sashiko-bot
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=20260816194836.C7D0B1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dawidro@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.