From: Harshal Dev <harshal.dev@oss.qualcomm.com>
To: Alexander Koskovich <akoskovich@pm.me>,
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-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v3 2/2] arm64: dts: qcom: sm8250: Add inline crypto engine
Date: Tue, 17 Mar 2026 14:57:18 +0530 [thread overview]
Message-ID: <f4358798-c40b-4425-9f7a-230cdc6398ce@oss.qualcomm.com> (raw)
In-Reply-To: <20260309-sm8250-ice-v3-2-418bf5c5c042@pm.me>
Hi Alexander,
On 3/10/2026 8:42 AM, Alexander Koskovich wrote:
> Add the ICE found on sm8250 and link it to the UFS node.
>
> qcom-ice 1d90000.crypto: Found QC Inline Crypto Engine (ICE) v3.1.81
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> Signed-off-by: Alexander Koskovich <akoskovich@pm.me>
> ---
> arch/arm64/boot/dts/qcom/sm8250.dtsi | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm8250.dtsi b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> index c7dffa440074..b49007934278 100644
> --- a/arch/arm64/boot/dts/qcom/sm8250.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> @@ -2513,6 +2513,8 @@ ufs_mem_hc: ufshc@1d84000 {
>
> power-domains = <&gcc UFS_PHY_GDSC>;
>
> + qcom,ice = <&ice>;
> +
> iommus = <&apps_smmu 0x0e0 0>, <&apps_smmu 0x4e0 0>;
>
> clock-names =
> @@ -2592,6 +2594,17 @@ ufs_mem_phy: phy@1d87000 {
> status = "disabled";
> };
>
> + ice: crypto@1d90000 {
> + compatible = "qcom,sm8250-inline-crypto-engine",
> + "qcom,inline-crypto-engine";
> + reg = <0 0x01d90000 0 0x8000>;
> + clocks = <&gcc GCC_UFS_PHY_ICE_CORE_CLK>,
> + <&gcc GCC_UFS_PHY_AHB_CLK>;
> + clock-names = "ice_core_clk",
> + "iface_clk";
As per comments on v2 of this patch, the clock names have been updated to 'core' and 'iface'.
Please update the same here since your patch depends on this one:
https://lore.kernel.org/all/20260317-qcom_ice_power_and_clk_vote-v3-1-53371dbabd6a@oss.qualcomm.com/
Regards,
Harshal
> + power-domains = <&gcc UFS_PHY_GDSC>;
> + };
> +
> cryptobam: dma-controller@1dc4000 {
> compatible = "qcom,bam-v1.7.4", "qcom,bam-v1.7.0";
> reg = <0 0x01dc4000 0 0x24000>;
>
prev parent reply other threads:[~2026-03-17 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 3:12 [PATCH v3 0/2] Enable inline crypto engine on SM8250 Alexander Koskovich
2026-03-10 3:12 ` [PATCH v3 1/2] dt-bindings: crypto: ice: Document sm8250 inline crypto engine Alexander Koskovich
2026-03-10 8:03 ` Krzysztof Kozlowski
2026-03-11 18:26 ` Krzysztof Kozlowski
2026-03-17 9:25 ` Harshal Dev
2026-03-10 3:12 ` [PATCH v3 2/2] arm64: dts: qcom: sm8250: Add " Alexander Koskovich
2026-03-10 14:11 ` Konrad Dybcio
2026-03-17 9:27 ` Harshal Dev [this message]
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=f4358798-c40b-4425-9f7a-230cdc6398ce@oss.qualcomm.com \
--to=harshal.dev@oss.qualcomm.com \
--cc=akoskovich@pm.me \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=herbert@gondor.apana.org.au \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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