lkml.org 
[lkml]   [2022]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [PATCH v7 6/9] crypto: qce: core: Add new compatibles for qce crypto driver
    From
    On 20/09/2022 13:40, Bhupesh Sharma wrote:
    > Since we decided to use soc specific compatibles for describing
    > the qce crypto IP nodes in the device-trees, adapt the driver
    > now to handle the same.
    >
    > Keep the old deprecated compatible strings still in the driver,
    > to ensure backward compatibility.
    >
    > Cc: Bjorn Andersson <andersson@kernel.org>
    > Cc: Rob Herring <robh@kernel.org>
    > Cc: herbert@gondor.apana.org.au
    > Tested-by: Jordan Crouse <jorcrous@amazon.com>
    > Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
    > ---
    > drivers/crypto/qce/core.c | 9 +++++++++
    > 1 file changed, 9 insertions(+)
    >
    > diff --git a/drivers/crypto/qce/core.c b/drivers/crypto/qce/core.c
    > index 63be06df5519..99ed540611ab 100644
    > --- a/drivers/crypto/qce/core.c
    > +++ b/drivers/crypto/qce/core.c
    > @@ -291,8 +291,17 @@ static int qce_crypto_remove(struct platform_device *pdev)
    > }
    >
    > static const struct of_device_id qce_crypto_of_match[] = {
    > + /* Following two entries are deprecated (kept only for backward compatibility) */
    > { .compatible = "qcom,crypto-v5.1", },
    > { .compatible = "qcom,crypto-v5.4", },

    This is okay, so there is no ABI break.

    > + /* Add compatible strings as per updated dt-bindings, here: */
    > + { .compatible = "qcom,ipq4019-qce", },
    > + { .compatible = "qcom,ipq6018-qce", },
    > + { .compatible = "qcom,ipq8074-qce", },
    > + { .compatible = "qcom,msm8996-qce", },
    > + { .compatible = "qcom,sdm845-qce", },
    > + { .compatible = "qcom,sm8150-qce", },
    > + { .compatible = "qcom,sm8250-qce", },

    This is a bit odd... you have 7 devices which are simply compatible or
    even the same. This should be instead one compatible.

    I don't really get why do you want to deprecate "qcom,crypto-v5.1".
    Commit msg only says "we decided" but I do not know who is "we" and "why
    we decided like this". If you want to deprecate it, perfectly fine by
    me, but please say in commit msg why you are doing it.

    Best regards,
    Krzysztof

    \
     
     \ /
      Last update: 2022-09-20 17:13    [W:4.465 / U:0.144 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site