linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Thara Gopinath <thara.gopinath@gmail.com>,
	Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Andy Gross <agross@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-crypto@vger.kernel.org
Subject: [PATCH v9 14/14] crypto: qce: core: Add a compatible based on a SoC name
Date: Wed,  8 Feb 2023 20:37:55 +0200	[thread overview]
Message-ID: <20230208183755.2907771-15-vladimir.zapolskiy@linaro.org> (raw)
In-Reply-To: <20230208183755.2907771-1-vladimir.zapolskiy@linaro.org>

The added 'qcom,ipq4019-qce' and 'qcom,sm8150-qce' compatible values will
serve as QCE IP family compatibles, so that the crypto engine on added
platforms can derive from one of these two. Also the compatibles serve as
a fall-back for currently supported QCE IP variants on Qualcomm platforms.

At the moment there is no need to differentiate or add any other SoC
specific compatible values to the list, however it's known in advance
that the two QCE IP families are not fully compatible between each other.

The IP version based compatibles are left untouched to preserve backward
DTB ABI compatibility.

Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
---
 drivers/crypto/qce/core.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/crypto/qce/core.c b/drivers/crypto/qce/core.c
index 8e496fb2d5e2..627354e772e9 100644
--- a/drivers/crypto/qce/core.c
+++ b/drivers/crypto/qce/core.c
@@ -293,6 +293,8 @@ static int qce_crypto_remove(struct platform_device *pdev)
 static const struct of_device_id qce_crypto_of_match[] = {
 	{ .compatible = "qcom,crypto-v5.1", },
 	{ .compatible = "qcom,crypto-v5.4", },
+	{ .compatible = "qcom,ipq4019-qce", },
+	{ .compatible = "qcom,sm8150-qce", },
 	{}
 };
 MODULE_DEVICE_TABLE(of, qce_crypto_of_match);
-- 
2.33.0


  parent reply	other threads:[~2023-02-08 18:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 18:37 [PATCH v9 00/14] crypto: qcom-qce: Add YAML bindings & support for newer SoCs Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 01/14] dt-bindings: qcom-qce: Convert bindings to yaml Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 02/14] MAINTAINERS: Add qcom-qce dt-binding file to QUALCOMM CRYPTO DRIVERS section Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 03/14] dt-bindings: qcom-qce: Add 'interconnects' and 'interconnect-names' Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 04/14] dt-bindings: qcom-qce: Add 'iommus' to optional properties Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 05/14] dt-bindings: qcom-qce: Add new SoC compatible strings for qcom-qce Vladimir Zapolskiy
2023-02-09  9:18   ` Krzysztof Kozlowski
2023-02-09  9:19     ` Krzysztof Kozlowski
2023-02-08 18:37 ` [PATCH v9 06/14] dt-bindings: qcom-qce: document optional clocks and clock-names properties Vladimir Zapolskiy
2023-02-09  9:20   ` Krzysztof Kozlowski
2023-02-10 11:17     ` Vladimir Zapolskiy
2023-02-10 11:30       ` Krzysztof Kozlowski
2023-02-08 18:37 ` [PATCH v9 07/14] arm: dts: qcom: ipq4019: update a compatible for QCE IP on IPQ4019 SoC Vladimir Zapolskiy
2023-02-09  9:22   ` Krzysztof Kozlowski
2023-02-08 18:37 ` [PATCH v9 08/14] arm64: dts: qcom: msm8996: update QCE compatible according to a new scheme Vladimir Zapolskiy
2023-02-09  9:23   ` Krzysztof Kozlowski
2023-02-08 18:37 ` [PATCH v9 09/14] arm64: dts: qcom: sdm845: " Vladimir Zapolskiy
2023-02-09  9:23   ` Krzysztof Kozlowski
2023-02-08 18:37 ` [PATCH v9 10/14] arm64: dts: qcom: sm8550: add a family compatible for QCE IP Vladimir Zapolskiy
2023-02-09  9:23   ` Krzysztof Kozlowski
2023-02-08 18:37 ` [PATCH v9 11/14] arm64: dts: qcom: sm8250: add description of Qualcomm Crypto Engine IP Vladimir Zapolskiy
2023-02-09 12:21   ` Bhupesh Sharma
2023-02-09 14:30     ` Vladimir Zapolskiy
2023-02-13 17:12       ` Bhupesh Sharma
2023-02-14 10:24         ` Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 12/14] crypto: qce: core: Add support to initialize interconnect path Vladimir Zapolskiy
2023-02-08 18:37 ` [PATCH v9 13/14] crypto: qce: core: Make clocks optional Vladimir Zapolskiy
2023-02-08 18:37 ` Vladimir Zapolskiy [this message]
2023-02-09  9:26   ` [PATCH v9 14/14] crypto: qce: core: Add a compatible based on a SoC name Krzysztof Kozlowski

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=20230208183755.2907771-15-vladimir.zapolskiy@linaro.org \
    --to=vladimir.zapolskiy@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bhupesh.sharma@linaro.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).