From: sashiko-bot@kernel.org
To: "Demeter Barna" <me@fromdisposition.org>,
"Abel Vesa" <abelvesa@kernel.org>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>
Cc: linux-crypto@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: sm8350: Add the inline crypto engine
Date: Mon, 09 Nov 2026 14:09:52 +0000 [thread overview]
Message-ID: <sashiko-outbox-205061@kernel.org> (raw)
In-Reply-To: <20261109-b4-sm8350-ice-v2-2-fd5e84985e90@fromdisposition.org>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] arm64: dts: qcom: sm8350: ICE reg size 0x11000 instead of
0x18000
--
commit b6d71a017150b9b7aef8d2a54ca324fd569ec504
Author: Demeter Barna <me@fromdisposition.org>
arm64: dts: qcom: sm8350: Add the inline crypto engine
This commit adds the UFS inline crypto engine (ICE) device node to the
SM8350 device tree and links it from the UFS host controller node via
qcom,ice.
> diff --git a/arch/arm64/boot/dts/qcom/sm8350.dtsi b/arch/arm64/boot/dts/qcom/sm8350.dtsi
> index 55b32050ce9c8..2b258c4b4fa71 100644
> --- a/arch/arm64/boot/dts/qcom/sm8350.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8350.dtsi
[ ... ]
> @@ -1807,6 +1809,17 @@ ufs_mem_phy: phy@1d87000 {
> status = "disabled";
> };
>
> + ice: crypto@1d88000 {
> + compatible = "qcom,sm8350-inline-crypto-engine",
> + "qcom,inline-crypto-engine";
> + reg = <0 0x01d88000 0 0x11000>;
[Severity: Low]
Should the ICE register region size be 0x18000 (0x8000 for ICE + 0x10000
for HWKM) instead of 0x11000?
Other Qualcomm SoCs with ICE v3.2.0+ and HWKM at 0x01d88000 define this
aperture as 0x18000, including Kodiak in fa9c7403af64 ("arm64: dts: qcom:
kodiak: Fix ICE reg size") and SM8450 in 7fb3d0512dac ("arm64: dts: qcom:
sm8450: Fix ICE reg size"). While drivers/soc/qcom/ice.c currently
accesses up to offset 0xd010 (QCOM_ICE_REG_HWKM_BANK0_BBAC_4), mapping
only 0x11000 leaves the upper 0x7000 bytes of the HWKM register space
unmapped.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109-b4-sm8350-ice-v2-0-fd5e84985e90@fromdisposition.org?part=2
next prev parent reply other threads:[~2026-11-09 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 13:55 [PATCH v2 0/2] arm64: dts: qcom: sm8350: Add the inline crypto engine Demeter Barna via B4 Relay
2026-11-09 13:55 ` [PATCH v2 1/2] dt-bindings: crypto: qcom,inline-crypto-engine: Add SM8350 Demeter Barna via B4 Relay
2026-11-10 11:52 ` Krzysztof Kozlowski
2026-11-09 13:55 ` [PATCH v2 2/2] arm64: dts: qcom: sm8350: Add the inline crypto engine Demeter Barna via B4 Relay
2026-11-09 14:09 ` sashiko-bot [this message]
2026-11-11 10:13 ` Abel Vesa
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=sashiko-outbox-205061@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=me@fromdisposition.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).