[v2,03/10] dt-bindings: qcom-qce: Fix compatibles combinations for SM8150 and IPQ4019 SoCs
Message ID | 20230322114519.3412469-4-bhupesh.sharma@linaro.org |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:604a:0:0:0:0:0 with SMTP id j10csp2302108wrt; Wed, 22 Mar 2023 05:05:45 -0700 (PDT) X-Google-Smtp-Source: AK7set/iK6XwqpjkTFg4Seo6UHoyeYG42VbOQZSIdEw5Lt1BY+d4USGFs9mO6Ekypkf20Dyc4ujr X-Received: by 2002:a17:903:22c6:b0:19c:b7da:fbdf with SMTP id y6-20020a17090322c600b0019cb7dafbdfmr3028671plg.26.1679486745522; Wed, 22 Mar 2023 05:05:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679486745; cv=none; d=google.com; s=arc-20160816; b=wHakK4frJ0W4QlGXrcqR9Pl9XwpgjV1OO0ZA9xuX/eDPTIj0Wbsx6iF79kDcN/X7Iv YvZhNBxCAeQYz8AKqfnz6EWjuWf2uZS5Rop4iPWEFKTWV+un3BaWIDnOD/iIzZOZZvWs PJacDrgvMvt4Z3VQPCMGxLbw3w4HsITbAEmz0x4MtStIYqvC83/7V5wW3acO4XToPGFg BsrdsK1iAv2rmHCcokZ02RLlaM97lZJYicgXoDlTUFOgEqvW2PsptLNJVxh3wwlXSPbb uggvarUMQald0ZXRDxxjycOcMfpOA7rQMerFVrAYYov0ccfscHEYKjsgopWuzaLc/CQp Symw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=ZX8cxV4gmi38o9Pi6mmNL+xnFc7tlNvHJgTN5N6z5i8=; b=DiMWFnif7vrqyu5HmAPRerZ28D2vwJI4D37jTNTmBwoEdJODI+x0X8qTdMDc5pECR5 JAK/baMDO/LjM1IcGxWTtuZ/JwkSlY6kjN2zdPA647Shj90V04QaJ0NBUq6oV3hPoKKI 0TmCpE9WpNkFtr9X+XavIfZMhPemqe6mCU5SXfkV926Rwi+yZlF8vSua+8UWlmroBR08 7NHE8JdJuIdQbqTmgwC1s8wsEQFFD3/l/nqF15hOJjQzNf1Bt3s7YsVkSamBxXM0LC45 KD4fMp8urbt4hgEmIEmte26APAti/H+J6DnYBPIGjIU5R2lMrEV4Vz+5FXm6Khj/w1Up a1PA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=AX9DZXXM; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id n14-20020a170902d2ce00b001a1b08aacedsi15227913plc.40.2023.03.22.05.05.00; Wed, 22 Mar 2023 05:05:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=AX9DZXXM; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229720AbjCVLqB (ORCPT <rfc822;pusanteemu@gmail.com> + 99 others); Wed, 22 Mar 2023 07:46:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48128 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230155AbjCVLpv (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 22 Mar 2023 07:45:51 -0400 Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2586460A8C for <linux-kernel@vger.kernel.org>; Wed, 22 Mar 2023 04:45:48 -0700 (PDT) Received: by mail-pl1-x62d.google.com with SMTP id c18so18985706ple.11 for <linux-kernel@vger.kernel.org>; Wed, 22 Mar 2023 04:45:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1679485547; 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=ZX8cxV4gmi38o9Pi6mmNL+xnFc7tlNvHJgTN5N6z5i8=; b=AX9DZXXME3un8pj7UdSfIKe1GjqelLDlEqm7BPP5UV7FblYgG1cQbIIyf3O9J41AM/ JoWdOMBL087P8bDBLKQ5pzNcXKZqRCrD8hnPw19kCG+jygl/BnNWuLzeTQdm8bcFVb7m Oy5ZxYG/14IANAFkHscVuUp3ZcdYVo8Fq5CZdDhkylXWzYVEbipT2hgiWuL++4dZbOk0 xu4hrlG+ibw6nCUcewjG/QOBO20rV83f56Unidsxc4U/8SUOR5I+ABSMjRSUUYKHATXY iCCT98hPzlZ/oGkGutxq4eRNk+Xwu3ijrPbwy7uCEE9qTcb9XwZxJQRWncdpRCO/yYf6 Muig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679485547; 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=ZX8cxV4gmi38o9Pi6mmNL+xnFc7tlNvHJgTN5N6z5i8=; b=tKuFyXj79WduNjDRjKyWa1kh2dz/uW90QYE7CWlW7ywH8ekl2h5BOyHTXtnz8DYruG 1Pil7Hz7tZSE/0MSjQQAClv3S2ujuRE/POo4ytheua5ghxZbEeZeGlJZmU1OXbz/lTjJ CZr/Bv+f0TcsR3HYky8Tih0tTIPsn4muaY3DnKC+PyZQjT98f6GBO/OQDhQKMUU7hkDD /GUcceuTJCE3Qa0cq9uKU8wwEWZHn1Wf+pciZ5iwvsF3kLiv2LnICSfFWGbCS3Fk8KnQ qHST7LQotUNuRCkQvRqpZG4kfaRt3+8GVvWM5Lw4HYmsX/pJy2JSbHcwD7EMTX9jQS4V 0cMA== X-Gm-Message-State: AO0yUKXoxMWtyidZfx39/GnoGrh9bDI72VVvAaykhiuXKJQ/tSA+R3Xj iNGepocHqauGzvb4BhU/Lsz2oQ== X-Received: by 2002:a17:90b:1e46:b0:23f:8752:98be with SMTP id pi6-20020a17090b1e4600b0023f875298bemr3535836pjb.4.1679485547584; Wed, 22 Mar 2023 04:45:47 -0700 (PDT) Received: from localhost.localdomain ([2401:4900:1c60:d4c3:8671:83c0:33ae:5a96]) by smtp.gmail.com with ESMTPSA id jd1-20020a170903260100b0019b0afc24e8sm10386649plb.250.2023.03.22.04.45.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 22 Mar 2023 04:45:47 -0700 (PDT) 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 v2 03/10] dt-bindings: qcom-qce: Fix compatibles combinations for SM8150 and IPQ4019 SoCs Date: Wed, 22 Mar 2023 17:15:12 +0530 Message-Id: <20230322114519.3412469-4-bhupesh.sharma@linaro.org> X-Mailer: git-send-email 2.38.1 In-Reply-To: <20230322114519.3412469-1-bhupesh.sharma@linaro.org> References: <20230322114519.3412469-1-bhupesh.sharma@linaro.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1761069493352825747?= X-GMAIL-MSGID: =?utf-8?q?1761069493352825747?= |
Series |
arm64: qcom: Enable Crypto Engine for a few Qualcomm SoCs
|
|
Commit Message
Bhupesh Sharma
March 22, 2023, 11:45 a.m. UTC
Currently the compatible list available in 'qce' dt-bindings does not
support SM8150 and IPQ4019 SoCs directly, leading to following
'dtbs_check' error:
arch/arm64/boot/dts/qcom/sm8150-sony-xperia-kumano-griffin.dtb:
crypto@1dfa000: compatible: 'oneOf' conditional failed, one must be fixed:
['qcom,sm8150-qce', 'qcom,qce'] is too long
['qcom,sm8150-qce', 'qcom,qce'] is too short
Fix the same.
Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
---
Documentation/devicetree/bindings/crypto/qcom-qce.yaml | 6 ++++++
1 file changed, 6 insertions(+)
Comments
Hi Bhupesh, On 3/22/23 13:45, Bhupesh Sharma wrote: > Currently the compatible list available in 'qce' dt-bindings does not > support SM8150 and IPQ4019 SoCs directly, leading to following > 'dtbs_check' error: > > arch/arm64/boot/dts/qcom/sm8150-sony-xperia-kumano-griffin.dtb: > crypto@1dfa000: compatible: 'oneOf' conditional failed, one must be fixed: > ['qcom,sm8150-qce', 'qcom,qce'] is too long > ['qcom,sm8150-qce', 'qcom,qce'] is too short > > Fix the same. > > Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org> > --- > Documentation/devicetree/bindings/crypto/qcom-qce.yaml | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml > index e375bd981300..90ddf98a6df9 100644 > --- a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml > +++ b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml > @@ -24,6 +24,12 @@ properties: > deprecated: true > description: Kept only for ABI backward compatibility > > + - items: > + - enum: > + - qcom,ipq4019-qce > + - qcom,sm8150-qce > + - const: qcom,qce > + thank you for the fix, the change is correct, please apply the tag: Fixes: 00f3bc2db351 ("dt-bindings: qcom-qce: Add new SoC compatible strings for Qualcomm QCE IP") But let me ask you to split the "items" into two: - items: - const: qcom,ipq4019-qce - const: qcom,qce - items: - const: qcom,sm8150-qce - const: qcom,qce and put each of these two new items below a list of compatible values, where a family compatible describes the list. Nevertheless, please also add my tag: Reviewed-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org> -- Best wishes, Vladimir
On 27/03/2023 13:49, Vladimir Zapolskiy wrote: > Hi Bhupesh, > > On 3/22/23 13:45, Bhupesh Sharma wrote: >> Currently the compatible list available in 'qce' dt-bindings does not >> support SM8150 and IPQ4019 SoCs directly, leading to following >> 'dtbs_check' error: >> >> arch/arm64/boot/dts/qcom/sm8150-sony-xperia-kumano-griffin.dtb: >> crypto@1dfa000: compatible: 'oneOf' conditional failed, one must be fixed: >> ['qcom,sm8150-qce', 'qcom,qce'] is too long >> ['qcom,sm8150-qce', 'qcom,qce'] is too short >> >> Fix the same. >> >> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org> >> --- >> Documentation/devicetree/bindings/crypto/qcom-qce.yaml | 6 ++++++ >> 1 file changed, 6 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml >> index e375bd981300..90ddf98a6df9 100644 >> --- a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml >> +++ b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml >> @@ -24,6 +24,12 @@ properties: >> deprecated: true >> description: Kept only for ABI backward compatibility >> >> + - items: >> + - enum: >> + - qcom,ipq4019-qce >> + - qcom,sm8150-qce >> + - const: qcom,qce >> + > > thank you for the fix, the change is correct, please apply the tag: > > Fixes: 00f3bc2db351 ("dt-bindings: qcom-qce: Add new SoC compatible strings for Qualcomm QCE IP") > > But let me ask you to split the "items" into two: > > - items: > - const: qcom,ipq4019-qce > - const: qcom,qce > > - items: > - const: qcom,sm8150-qce > - const: qcom,qce > Why splitting these? The enum is the preferred way usually, so why here do it differently? Best regards, Krzysztof
On Mon, 27 Mar 2023 at 17:49, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > > On 27/03/2023 13:49, Vladimir Zapolskiy wrote: > > Hi Bhupesh, > > > > On 3/22/23 13:45, Bhupesh Sharma wrote: > >> Currently the compatible list available in 'qce' dt-bindings does not > >> support SM8150 and IPQ4019 SoCs directly, leading to following > >> 'dtbs_check' error: > >> > >> arch/arm64/boot/dts/qcom/sm8150-sony-xperia-kumano-griffin.dtb: > >> crypto@1dfa000: compatible: 'oneOf' conditional failed, one must be fixed: > >> ['qcom,sm8150-qce', 'qcom,qce'] is too long > >> ['qcom,sm8150-qce', 'qcom,qce'] is too short > >> > >> Fix the same. > >> > >> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org> > >> --- > >> Documentation/devicetree/bindings/crypto/qcom-qce.yaml | 6 ++++++ > >> 1 file changed, 6 insertions(+) > >> > >> diff --git a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml > >> index e375bd981300..90ddf98a6df9 100644 > >> --- a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml > >> +++ b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml > >> @@ -24,6 +24,12 @@ properties: > >> deprecated: true > >> description: Kept only for ABI backward compatibility > >> > >> + - items: > >> + - enum: > >> + - qcom,ipq4019-qce > >> + - qcom,sm8150-qce > >> + - const: qcom,qce > >> + > > > > thank you for the fix, the change is correct, please apply the tag: > > > > Fixes: 00f3bc2db351 ("dt-bindings: qcom-qce: Add new SoC compatible strings for Qualcomm QCE IP") > > > > But let me ask you to split the "items" into two: > > > > - items: > > - const: qcom,ipq4019-qce > > - const: qcom,qce > > > > - items: > > - const: qcom,sm8150-qce > > - const: qcom,qce > > > > Why splitting these? The enum is the preferred way usually, so why here > do it differently? Exactly, so our compatibles as per my patch can be : "qcom,ipq4019-qce", "qcom,qce" or "qcom,sm8150-qce", "qcom,qce" which is what we want to achieve as these are the base compatible versions for further socs, with compatible strings as: "qcom,<new-soc-with-crypto-same-as-ipq4019-qce", "qcom,ipq4019-qce", "qcom,qce" , or "qcom,<new-soc-with-crypto-same-as-sm8150-qce", "qcom,sm8150-qce", "qcom,qce" Thanks, Bhupesh
diff --git a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml index e375bd981300..90ddf98a6df9 100644 --- a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml +++ b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml @@ -24,6 +24,12 @@ properties: deprecated: true description: Kept only for ABI backward compatibility + - items: + - enum: + - qcom,ipq4019-qce + - qcom,sm8150-qce + - const: qcom,qce + - items: - enum: - qcom,ipq6018-qce