From: "Rob Herring (Arm)" <robh@kernel.org>
To: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
Cc: aiqun.yu@oss.qualcomm.com,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, tingwei.zhang@oss.qualcomm.com,
yijie.yang@oss.qualcomm.com, trilok.soni@oss.qualcomm.com,
"David S. Miller" <davem@davemloft.net>,
Vinod Koul <vkoul@kernel.org>,
linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>
Subject: Re: [PATCH v2 2/3] dt-bindings: crypto: qcom,inline-crypto-engine: Document Maili ICE
Date: Tue, 30 Jun 2026 12:41:36 -0500 [thread overview]
Message-ID: <178284129608.4118791.8314319261114374881.robh@kernel.org> (raw)
In-Reply-To: <20260628-maili-crypto-v2-2-f8ce760f71d6@oss.qualcomm.com>
On Sun, 28 Jun 2026 23:44:36 -0700, Jingyi Wang wrote:
> The Inline Crypto Engine found on Maili SoC is compatible with the common
> baseline IP 'qcom,inline-crypto-engine' and requires the UFS_PHY_GDSC
> power-domain and iface clock. Hence, document the compatible as such.
>
> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
> ---
> Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-06-30 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 6:44 [PATCH v2 0/3] dt-bindings: crypto: Add Qualcomm Maili crypto support Jingyi Wang
2026-06-29 6:44 ` [PATCH v2 1/3] dt-bindings: crypto: qcom,prng: Document Maili TRNG Jingyi Wang
2026-06-29 6:44 ` [PATCH v2 2/3] dt-bindings: crypto: qcom,inline-crypto-engine: Document Maili ICE Jingyi Wang
2026-06-30 17:41 ` Rob Herring (Arm) [this message]
2026-06-29 6:44 ` [PATCH v2 3/3] dt-bindings: crypto: qcom,ice: Fix missing power-domain and iface clk on Hawi Jingyi Wang
2026-06-30 17:47 ` Rob Herring (Arm)
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=178284129608.4118791.8314319261114374881.robh@kernel.org \
--to=robh@kernel.org \
--cc=aiqun.yu@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=jingyi.wang@oss.qualcomm.com \
--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=tingwei.zhang@oss.qualcomm.com \
--cc=trilok.soni@oss.qualcomm.com \
--cc=vkoul@kernel.org \
--cc=yijie.yang@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