From: Rob Herring <robh@kernel.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: devicetree@vger.kernel.org, agross@kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
andersson@kernel.org, bhupesh.linux@gmail.com,
linux-crypto@vger.kernel.org, krzysztof.kozlowski@linaro.org,
konrad.dybcio@linaro.org, vladimir.zapolskiy@linaro.org
Subject: Re: [PATCH 1/1] dt-bindings: qcom-qce: Add compatibles for SM6115 and QCS2290
Date: Tue, 21 Mar 2023 16:31:39 -0500 [thread overview]
Message-ID: <20230321213139.GA1646917-robh@kernel.org> (raw)
In-Reply-To: <20230320073816.3012198-1-bhupesh.sharma@linaro.org>
On Mon, Mar 20, 2023 at 01:08:16PM +0530, Bhupesh Sharma wrote:
> Crypto Engine block on Qualcomm SoCs SM6115 and QCS2290
> do not require clocks strictly, so add compatibles for these
> SoCs, indicating that they are similar to the flavour
> found on SM8150.
>
> 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 e375bd981300..e6840d124af3 100644
> --- a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml
> +++ b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml
> @@ -35,10 +35,12 @@ properties:
>
> - items:
> - enum:
> + - qcom,sm6115-qce
> - qcom,sm8250-qce
> - qcom,sm8350-qce
> - qcom,sm8450-qce
> - qcom,sm8550-qce
> + - qcom,qcs2290-qce
'q' goes before 's'
> - const: qcom,sm8150-qce
> - const: qcom,qce
>
> --
> 2.38.1
>
next prev parent reply other threads:[~2023-03-21 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 7:38 [PATCH 1/1] dt-bindings: qcom-qce: Add compatibles for SM6115 and QCS2290 Bhupesh Sharma
2023-03-21 21:31 ` Rob Herring [this message]
2023-03-22 8:32 ` 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=20230321213139.GA1646917-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=bhupesh.sharma@linaro.org \
--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=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).