From: Bhupesh Sharma <bhupesh.sharma@linaro.org>
To: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Cc: agross@kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, andersson@kernel.org,
bhupesh.sharma@linaro.org, bhupesh.linux@gmail.com,
krzysztof.kozlowski@linaro.org, robh+dt@kernel.org,
konrad.dybcio@linaro.org, vladimir.zapolskiy@linaro.org,
rfoss@kernel.org, neil.armstrong@linaro.org
Subject: [PATCH v4 06/11] dt-bindings: qcom-qce: Add compatibles for SM6115 and QCM2290
Date: Fri, 31 Mar 2023 22:13:18 +0530 [thread overview]
Message-ID: <20230331164323.729093-7-bhupesh.sharma@linaro.org> (raw)
In-Reply-To: <20230331164323.729093-1-bhupesh.sharma@linaro.org>
Crypto Engine block on Qualcomm SoCs SM6115 and QCM2290
do not require clocks strictly, so add compatibles for these
SoCs, indicating that they are similar to the flavour
found on SM8150.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
---
Documentation/devicetree/bindings/crypto/qcom-qce.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml
index 90ddf98a6df9..82ea97568008 100644
--- a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml
+++ b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml
@@ -41,6 +41,8 @@ properties:
- items:
- enum:
+ - qcom,qcm2290-qce
+ - qcom,sm6115-qce
- qcom,sm8250-qce
- qcom,sm8350-qce
- qcom,sm8450-qce
--
2.38.1
next prev parent reply other threads:[~2023-03-31 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 16:43 [PATCH v4 00/11] arm64: qcom: Enable Crypto Engine for a few Qualcomm SoCs Bhupesh Sharma
2023-03-31 16:43 ` [PATCH v4 01/11] dt-bindings: dma: Add support for SM6115 and QCM2290 SoCs Bhupesh Sharma
2023-03-31 16:43 ` [PATCH v4 02/11] dt-bindings: dma: Increase iommu maxItems for BAM DMA Bhupesh Sharma
2023-03-31 16:43 ` [PATCH v4 03/11] arm64: dts: qcom: sdm8550: Fix the BAM DMA engine compatible string Bhupesh Sharma
2023-03-31 19:54 ` Konrad Dybcio
2023-03-31 16:43 ` [PATCH v4 04/11] arm64: dts: qcom: sdm845: Fix the slimbam " Bhupesh Sharma
2023-03-31 19:55 ` Konrad Dybcio
2023-03-31 16:43 ` [PATCH v4 05/11] dt-bindings: qcom-qce: Fix compatible combinations for SM8150 and IPQ4019 SoCs Bhupesh Sharma
2023-03-31 16:43 ` Bhupesh Sharma [this message]
2023-03-31 16:43 ` [PATCH v4 07/11] arm64: dts: qcom: sm6115: Add Crypto Engine support Bhupesh Sharma
2023-03-31 16:43 ` [PATCH v4 08/11] arm64: dts: qcom: sm8150: " Bhupesh Sharma
2023-03-31 16:43 ` [PATCH v4 09/11] arm64: dts: qcom: sm8250: " Bhupesh Sharma
2023-03-31 16:43 ` [PATCH v4 10/11] arm64: dts: qcom: sm8350: " Bhupesh Sharma
2023-03-31 16:43 ` [PATCH v4 11/11] arm64: dts: qcom: sm8450: add crypto nodes 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=20230331164323.729093-7-bhupesh.sharma@linaro.org \
--to=bhupesh.sharma@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--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=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh+dt@kernel.org \
--cc=vladimir.zapolskiy@linaro.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;
as well as URLs for NNTP newsgroup(s).