From: Harshal Dev <harshal.dev@oss.qualcomm.com>
To: Wenjia Zhang <wenjia.zhang@oss.qualcomm.com>
Cc: kernel@quicinc.com, linux-arm-msm@vger.kernel.org,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Konrad Dybcio <konradybcio@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: hamoa: Add ICE node for UFS inline encryption
Date: Tue, 21 Jul 2026 15:23:45 +0530 [thread overview]
Message-ID: <574de566-e594-489a-be43-012fb9f4d906@oss.qualcomm.com> (raw)
In-Reply-To: <20260721-devtool-v1-2-ade633accb41@oss.qualcomm.com>
Hi Wenjia,
On 21-07-2026 02:52 pm, Wenjia Zhang wrote:
> Add the Inline Crypto Engine (ICE) device node to enable hardware-
Nit: We're not 'enabling' but 'describing' hardware that is present on the SoC.
I suggest we re-phrase the wording to reflect that.
Regards,
Harshal
> accelerated inline encryption for UFS storage on the Hamoa IoT EVK
> board (Qualcomm X1E80100 SoC).
>
> Signed-off-by: Wenjia Zhang <wenjia.zhang@oss.qualcomm.com>
> ---
> arch/arm64/boot/dts/qcom/hamoa.dtsi | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
prev parent reply other threads:[~2026-07-21 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 9:22 [PATCH 0/2] Enable ICE for UFS on Hamoa IoT EVK Wenjia Zhang
2026-07-21 9:22 ` [PATCH 1/2] dt-bindings: crypto: qcom,inline-crypto-engine: Add x1e80100 support Wenjia Zhang
2026-07-21 9:22 ` [PATCH 2/2] arm64: dts: qcom: hamoa: Add ICE node for UFS inline encryption Wenjia Zhang
2026-07-21 9:53 ` 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=574de566-e594-489a-be43-012fb9f4d906@oss.qualcomm.com \
--to=harshal.dev@oss.qualcomm.com \
--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=kernel@quicinc.com \
--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 \
--cc=wenjia.zhang@oss.qualcomm.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