From mboxrd@z Thu Jan 1 00:00:00 1970 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 71081ECAAD8 for ; Tue, 20 Sep 2022 07:31:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229695AbiITHbv (ORCPT ); Tue, 20 Sep 2022 03:31:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36722 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229684AbiITHbr (ORCPT ); Tue, 20 Sep 2022 03:31:47 -0400 Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8EDA95C9DC for ; Tue, 20 Sep 2022 00:31:45 -0700 (PDT) Received: by mail-lf1-x131.google.com with SMTP id a3so2312430lfk.9 for ; Tue, 20 Sep 2022 00:31:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date; bh=jnQTMRJFYigIA33SCaz3qFtz2tTG96QP1qgq/1/BZcI=; b=T0y+y6A1fvkqDFPe4IcALqvk6i6V6IeL/T42HmYnQ/iEvssRXvoGNXQK2QK2l9krs8 ylSJI39dQ1svBpruOpx9+f+Ti7Ty1xvoVCbTtSyd87OSudH/Dup9M1gCQNKxfjuCXBsy ercJGw3wc4E+wz7EbEXGNAW6IKHGrRUMcA5bMbFoDcZN7drVoWGhZaAc9nZClDsM5iK1 +H/cnT2lvzgTLxqmC7dzTkaSeJ/SUIjZeDHmgWGe9FgFqwxbqcfAAUA70/5ZElnLMWEK rtOlV7Zd86Ul81C3ho1Js8L556epC32JMPNCrD74SoiMxcBe1rQ0fY8ypwKrdXqi5DCq F8fA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date; bh=jnQTMRJFYigIA33SCaz3qFtz2tTG96QP1qgq/1/BZcI=; b=1DlVWh+gd7eRjnoH0z7AhmdupHwJY8qhX6dOyj+v6F/UuF047xZ8FAWi48+etk8gpR p7JapG9SwKvzvfewBPo2zYYyUeBVEe2pJJ528EvFHLgxxUzmj5iKhxgx2Xsc3V9Fhz2b OWo22xXk1KmEF54a82Xd7k1C2WT78r681+RRnMkyBOQPWOFl67+0mwgd9NuCYaGfCc2s aWLWUjWZHna/DuYxi6kaL9cHSEzt95CDhvN6uO3jsvxNy3dlD41t2NqAeSoCHK4BXy+O DjddCyzTjYDk6A8i4F6UUr/hlXMijE7290LXFugp3cxiMw7a6ZX0LA6R1Rnr5H1J6J1B cIng== X-Gm-Message-State: ACrzQf1ejRRBRsnIx8Yp5aKqsDV4yrFAWn8ANgjTa+nXwuiZhnNFHR14 hU7lTg0Bm+8EwJ/5hjq6m+Uu3A== X-Google-Smtp-Source: AMsMyM5yIu9IkKRq6w5n9mdk+CKiqWTaJs++Wf9rCvN4lj2CHpn0F5WW7oZBBev+DaqYQIfxRg/R4Q== X-Received: by 2002:a05:6512:6d6:b0:499:27c:1aa0 with SMTP id u22-20020a05651206d600b00499027c1aa0mr7981676lff.88.1663659103935; Tue, 20 Sep 2022 00:31:43 -0700 (PDT) Received: from [192.168.0.21] (78-11-189-27.static.ip.netia.com.pl. [78.11.189.27]) by smtp.gmail.com with ESMTPSA id q25-20020a2e8759000000b0026c2e0258bcsm125089ljj.42.2022.09.20.00.31.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Sep 2022 00:31:42 -0700 (PDT) Message-ID: <30756e6f-952f-ccf2-b493-e515ba4f0a64@linaro.org> Date: Tue, 20 Sep 2022 09:31:41 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 Subject: Re: [PATCH v6 4/4] dt-bindings: qcom-qce: Add new SoC compatible strings in dt-binding doc Content-Language: en-US To: Bhupesh Sharma , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Cc: agross@kernel.org, robh+dt@kernel.org, linux-arm-msm@vger.kernel.org, thara.gopinath@gmail.com, robh@kernel.org, andersson@kernel.org, bhupesh.linux@gmail.com, Jordan Crouse References: <20220919195618.926227-1-bhupesh.sharma@linaro.org> <20220919195618.926227-5-bhupesh.sharma@linaro.org> From: Krzysztof Kozlowski In-Reply-To: <20220919195618.926227-5-bhupesh.sharma@linaro.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 19/09/2022 21:56, Bhupesh Sharma wrote: > Newer Qualcomm chips support newer versions of the qce crypto IP, so add > soc specific compatible strings for qcom-qce instead of using crypto > IP version specific ones. > > Keep the old strings for backward-compatibility, but mark them as > deprecated. > > Cc: Bjorn Andersson > Reviewed-by: Rob Herring > Tested-by: Jordan Crouse > Signed-off-by: Bhupesh Sharma > --- > .../devicetree/bindings/crypto/qcom-qce.yaml | 12 ++++++++++-- > 1 file changed, 10 insertions(+), 2 deletions(-) > > diff --git a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml > index 4e00e7925fed..aa2f676f5382 100644 > --- a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml > +++ b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml > @@ -15,7 +15,15 @@ description: > > properties: > compatible: > - const: qcom,crypto-v5.1 > + enum: > + - qcom,crypto-v5.1 # Deprecated. Kept only for backward compatibility deprecated:true in its own oneOf entry (see other examples). > + - qcom,ipq6018-qce > + - qcom,ipq8074-qce > + - qcom,msm8996-qce > + - qcom,sdm845-qce > + - qcom,sm8150-qce > + - qcom,sm8250-qce > + - qcom,sm8350-qce Entire change is not backwards compatible thus not bisectable and not ABI-safe. Best regards, Krzysztof