From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Shawn Guo <shengchao.guo@oss.qualcomm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
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>,
Dmitry Baryshkov <lumag@kernel.org>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Harshal Dev <harshal.dev@oss.qualcomm.com>,
Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
Subject: Re: [PATCH RESEND] dt-bindings: crypto: qcom,inline-crypto-engine: Document Nord ICE
Date: Mon, 6 Jul 2026 19:33:37 +0200 [thread overview]
Message-ID: <549ff994-6b6d-49c3-a764-4c1e134a4a14@kernel.org> (raw)
In-Reply-To: <CAMRc=Mcg-6XajFJCjTDgGACQ7YLGggw5TEtHv4QMEA=dFLOhTg@mail.gmail.com>
On 06/07/2026 19:13, Bartosz Golaszewski wrote:
> On Mon, 6 Jul 2026 08:54:22 +0200, Krzysztof Kozlowski <krzk@kernel.org> said:
>> On Sun, Jul 05, 2026 at 11:15:45PM +0530, Kuldeep Singh wrote:
>>> On 04-07-2026 06:14, Shawn Guo wrote:
>>>> Document Inline Crypto Engine (ICE) on Qualcomm Nord SoC.
>>>>
>>>> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>>>> Reviewed-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
>>>> Signed-off-by: Shawn Guo <shengchao.guo@oss.qualcomm.com>
>>>> ---
>>>> It was included in the Nord SA8797P DTS series [1] due to that
>>>> the prerequisite changes were picked up by Bjorn for 7.2. Resend it to
>>>> Herbert as the dependency is gone now with 7.2-rc1.
>>>>
>>>> [1] https://lore.kernel.org/all/20260526051300.1669201-1-shengchao.guo@oss.qualcomm.com/
>>>>
>>>> .../devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml | 2 ++
>>>> 1 file changed, 2 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml b/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
>>>> index db895c50e2d2..d690eff2e86d 100644
>>>> --- a/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
>>>> +++ b/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
>>>> @@ -17,6 +17,7 @@ properties:
>>>> - qcom,hawi-inline-crypto-engine
>>>> - qcom,kaanapali-inline-crypto-engine
>>>> - qcom,milos-inline-crypto-engine
>>>> + - qcom,nord-inline-crypto-engine
>>>> - qcom,qcs8300-inline-crypto-engine
>>>> - qcom,sa8775p-inline-crypto-engine
>>>> - qcom,sc7180-inline-crypto-engine
>>>> @@ -63,6 +64,7 @@ allOf:
>>>> enum:
>>>> - qcom,eliza-inline-crypto-engine
>>>> - qcom,milos-inline-crypto-engine
>>>> + - qcom,nord-inline-crypto-engine
>>>
>>> With below patch, we don't need nord entry here.
>>> https://lore.kernel.org/lkml/20260702-b4-shikra_crypto_changse-v2-1-66173f2f28b3@qti.qualcomm.com/
>>
>> Patch has conflict. This (Nord) should go after above one, with this
>> fixed.
>>
>
> The other series still hasn't made its way upstream. This one's simple, can we
> queue it now and rebase the other one?
This is not point of rebase, but conflicting work.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-07-06 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 0:44 [PATCH RESEND] dt-bindings: crypto: qcom,inline-crypto-engine: Document Nord ICE Shawn Guo
2026-07-05 17:45 ` Kuldeep Singh
2026-07-06 6:54 ` Krzysztof Kozlowski
2026-07-06 17:13 ` Bartosz Golaszewski
2026-07-06 17:33 ` Krzysztof Kozlowski [this message]
2026-07-06 18:25 ` Kuldeep Singh
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=549ff994-6b6d-49c3-a764-4c1e134a4a14@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=deepti.jaggi@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=harshal.dev@oss.qualcomm.com \
--cc=herbert@gondor.apana.org.au \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=kuldeep.singh@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=robh@kernel.org \
--cc=shengchao.guo@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