Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C4C95C636D6 for ; Wed, 22 Feb 2023 17:23:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232642AbjBVRXI (ORCPT ); Wed, 22 Feb 2023 12:23:08 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37270 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232678AbjBVRW7 (ORCPT ); Wed, 22 Feb 2023 12:22:59 -0500 Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BD85776BB for ; Wed, 22 Feb 2023 09:22:55 -0800 (PST) Received: by mail-lj1-x229.google.com with SMTP id z42so881314ljq.13 for ; Wed, 22 Feb 2023 09:22:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1677086574; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=bNKLwBHwPw1lEE61Bg4S2Go1fSCcBOdaNH5bLSqYv1w=; b=EQLZNzI8AvFJUtLVK9f6DK297fposcITZsp2J7KwKNSZWYLlxU4w77W25G1CR7FECR yv/31F2Op++wZdwDcMPrEDRyDjOEDPcsquKOeKrkosJs7w2XGuP1AWOFvBszyDnbRHSu jDMqlFCFt0a+oL5Hz/JKj0apuqDA/wRExLYJbaISbpwi/T9m08lOgES/ZgSzdBCabFOb j9DG9+F7i6Uf+xjBcQInftSQZweSqJI313KlnB2QMg432ULvSRVns0GguqraYCtJtMcg VuMthb9hNN9Nsl+ICC/s40UfEilgEUZdKuA5K8TSoFsX4czij2Xk5Fto/2QzjcBk1Pq2 QHHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677086574; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=bNKLwBHwPw1lEE61Bg4S2Go1fSCcBOdaNH5bLSqYv1w=; b=JFHP9WgNNxXM3iN2SZEm0Qqq195XcxwLgDj3DFG3HvS9Dk3ow1ajkOJaqFSMsMKsHb RNDO4Vg8VegrNShcm48ohmpuE3A4z+tNv5EDfwgeS9/BzQly5xRfv/+e2shm3SrCBKru //bYL0F5W8CLQm2UD6CfRum1rfUeD7J81LcsY9E18/GiWOribbKwEdnXcZW7FAwkv9CH v8g/aELTDrrXKx4sPCPg5pbIxbblPgDnjvXCL/NJ3MkPG01lgd/mfRrXSwsC3Xcc2Thp Q9doYxzEpGJwrBVcQxaExmDakDAPJUin038A9XCB8/wtM8n1UU+Dc4G9irxUOGo7YMUi SBfA== X-Gm-Message-State: AO0yUKXaG5MPSJXyfQTLC6a4pVGMVZ04bERfZL1tRrbp2/gS8P88fIrn 9ufiD+g5p7ejyQAHwcRehr130Q== X-Google-Smtp-Source: AK7set8IqwOJCZ/gUltz5168tjCvqYLrDlXIy85IPgsxTpPrdxapHrvrE8RxvjWTYrve8QPNPjfM+Q== X-Received: by 2002:a2e:3008:0:b0:294:70b7:ff90 with SMTP id w8-20020a2e3008000000b0029470b7ff90mr3027118ljw.0.1677086573884; Wed, 22 Feb 2023 09:22:53 -0800 (PST) Received: from localhost.localdomain (88-112-131-206.elisa-laajakaista.fi. [88.112.131.206]) by smtp.gmail.com with ESMTPSA id r3-20020a2e80c3000000b0029358afcc9esm805233ljg.34.2023.02.22.09.22.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 22 Feb 2023 09:22:52 -0800 (PST) From: Vladimir Zapolskiy To: Krzysztof Kozlowski , Bjorn Andersson , Herbert Xu , Thara Gopinath , Bhupesh Sharma Cc: Rob Herring , Konrad Dybcio , Andy Gross , "David S. Miller" , devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org, Neil Armstrong , Krzysztof Kozlowski Subject: [PATCH v11 05/10] dt-bindings: qcom-qce: Add new SoC compatible strings for Qualcomm QCE IP Date: Wed, 22 Feb 2023 19:22:35 +0200 Message-Id: <20230222172240.3235972-6-vladimir.zapolskiy@linaro.org> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20230222172240.3235972-1-vladimir.zapolskiy@linaro.org> References: <20230222172240.3235972-1-vladimir.zapolskiy@linaro.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Introduce a generic IP family compatible 'qcom,qce' and its two derivatives based on SoC names rather than on IP versions. Having a generic compatible is only partially sufficient, the QCE IP version can be discovered in runtime, however there are two known groups of QCE IP versions, which require different DT properties, these two groups are populated with SoC based compatibles known at the moment. Keep the old compatible 'qcom,crypto-v5.1' and document an existing and already used but not previously documented compatible 'qcom,crypto-v5.4' for backward compatibility of DTB ABI, mark both of the compatibles as deprecated. The change is based on the original one written by Bhupesh Sharma, adding a generic family compatible is suggested by Neil Armstrong. Cc: Bhupesh Sharma Cc: Neil Armstrong Reviewed-by: Krzysztof Kozlowski Signed-off-by: Vladimir Zapolskiy --- .../devicetree/bindings/crypto/qcom-qce.yaml | 29 +++++++++++++++++-- 1 file changed, 27 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml index 4e00e7925fed..84f57f44bb71 100644 --- a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml +++ b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml @@ -15,7 +15,32 @@ description: properties: compatible: - const: qcom,crypto-v5.1 + oneOf: + - const: qcom,crypto-v5.1 + deprecated: true + description: Kept only for ABI backward compatibility + + - const: qcom,crypto-v5.4 + deprecated: true + description: Kept only for ABI backward compatibility + + - items: + - enum: + - qcom,ipq6018-qce + - qcom,ipq8074-qce + - qcom,msm8996-qce + - qcom,sdm845-qce + - const: qcom,ipq4019-qce + - const: qcom,qce + + - items: + - enum: + - qcom,sm8250-qce + - qcom,sm8350-qce + - qcom,sm8450-qce + - qcom,sm8550-qce + - const: qcom,sm8150-qce + - const: qcom,qce reg: maxItems: 1 @@ -70,7 +95,7 @@ examples: - | #include crypto-engine@fd45a000 { - compatible = "qcom,crypto-v5.1"; + compatible = "qcom,ipq6018-qce", "qcom,ipq4019-qce", "qcom,qce"; reg = <0xfd45a000 0x6000>; clocks = <&gcc GCC_CE2_AHB_CLK>, <&gcc GCC_CE2_AXI_CLK>, -- 2.33.0