From: Bhupesh Sharma <bhupesh.sharma@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org
Cc: agross@kernel.org, herbert@gondor.apana.org.au,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
linux-arm-msm@vger.kernel.org, thara.gopinath@gmail.com,
robh@kernel.org, andersson@kernel.org, bhupesh.linux@gmail.com,
davem@davemloft.net, Jordan Crouse <jorcrous@amazon.com>
Subject: Re: [PATCH v7 4/9] dt-bindings: qcom-qce: Add new SoC compatible strings for qcom-qce
Date: Wed, 21 Sep 2022 11:30:46 +0530 [thread overview]
Message-ID: <05a1447e-51b1-cd6b-36bc-98f011e786e0@linaro.org> (raw)
In-Reply-To: <0a6b443c-33b4-5fc7-5a2f-e55f5387999f@linaro.org>
On 9/20/22 8:40 PM, Krzysztof Kozlowski wrote:
> On 20/09/2022 13:40, Bhupesh Sharma wrote:
>> Newer Qualcomm chips support newer versions of the qce crypto IP, so add
>> soc specific compatible strings for qcom-qce instead of using crypto
>> IP version specific ones.
>>
>> Keep the old strings for backward-compatibility, but mark them as
>> deprecated.
>>
>> Cc: Bjorn Andersson <andersson@kernel.org>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>> Tested-by: Jordan Crouse <jorcrous@amazon.com>
>> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
>> ---
>> .../devicetree/bindings/crypto/qcom-qce.yaml | 12 ++++++++++--
>> 1 file changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml
>> index 4e00e7925fed..aa2f676f5382 100644
>> --- a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml
>> +++ b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml
>> @@ -15,7 +15,15 @@ description:
>>
>> properties:
>> compatible:
>> - const: qcom,crypto-v5.1
>> + enum:
>> + - qcom,crypto-v5.1 # Deprecated. Kept only for backward compatibility
>
> No changes since v6.
Right. v7 is just to propose the new subset of patchsets and ordering
(since we changed it from v5 - which was a single patchset) and get some
early feedback and comments and get to know if the respective
maintainers are fine with the patch ordering, cc-list etc.
I will surely include your comments in v8.
Thanks,
Bhupesh
next prev parent reply other threads:[~2022-09-21 6:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 11:40 [PATCH v7 0/9] crypto: qcom-qce: Add YAML bindings & support for newer SoCs Bhupesh Sharma
2022-09-20 11:40 ` [PATCH v7 1/9] dt-bindings: qcom-qce: Convert bindings to yaml Bhupesh Sharma
2022-09-20 11:40 ` [PATCH v7 2/9] dt-bindings: qcom-qce: Add 'interconnects' and 'interconnect-names' Bhupesh Sharma
2022-09-20 11:40 ` [PATCH v7 3/9] dt-bindings: qcom-qce: Add 'iommus' to optional properties Bhupesh Sharma
2022-09-20 11:40 ` [PATCH v7 4/9] dt-bindings: qcom-qce: Add new SoC compatible strings for qcom-qce Bhupesh Sharma
2022-09-20 15:10 ` Krzysztof Kozlowski
2022-09-21 6:00 ` Bhupesh Sharma [this message]
2022-09-20 11:40 ` [PATCH v7 5/9] crypto: qce: core: Add support to initialize interconnect path Bhupesh Sharma
2022-09-20 11:40 ` [PATCH v7 6/9] crypto: qce: core: Add new compatibles for qce crypto driver Bhupesh Sharma
2022-09-20 15:12 ` Krzysztof Kozlowski
2022-09-21 6:16 ` Bhupesh Sharma
2022-09-21 6:27 ` Krzysztof Kozlowski
2022-09-21 6:52 ` Bhupesh Sharma
2022-11-07 3:43 ` Bjorn Andersson
2022-11-07 9:07 ` Krzysztof Kozlowski
2022-09-20 11:40 ` [PATCH v7 7/9] crypto: qce: core: Make clocks optional Bhupesh Sharma
2022-09-20 11:40 ` [PATCH v7 8/9] MAINTAINERS: Add qcom-qce dt-binding file to QUALCOMM CRYPTO DRIVERS section Bhupesh Sharma
2022-09-20 11:40 ` [PATCH v7 9/9] MAINTAINERS: Add myself as a co-maintainer for Qualcomm Crypto Drivers Bhupesh Sharma
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=05a1447e-51b1-cd6b-36bc-98f011e786e0@linaro.org \
--to=bhupesh.sharma@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jorcrous@amazon.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=thara.gopinath@gmail.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