[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ccc318c0-ee1b-d538-6d2b-bf85a3c9c6fd@linaro.org>
Date: Tue, 20 Sep 2022 11:39:29 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Bhupesh Sharma <bhupesh.sharma@...aro.org>,
linux-arm-kernel@...ts.infradead.org, linux-arm-msm@...r.kernel.org
Cc: agross@...nel.org, linux-kernel@...r.kernel.org,
robh+dt@...nel.org, thara.gopinath@...il.com,
devicetree@...r.kernel.org, robh@...nel.org, andersson@...nel.org,
bhupesh.linux@...il.com, catalin.marinas@....com, will@...nel.org,
arnd@...db.de, Jordan Crouse <jorcrous@...zon.com>
Subject: Re: [PATCH v6 1/4 RESEND] ARM: dts: qcom: Use new compatibles for
crypto nodes
On 20/09/2022 10:57, Bhupesh Sharma wrote:
>>> crypto: crypto@...a000 {
>>> - compatible = "qcom,crypto-v5.1";
>>> + compatible = "qcom,ipq4019-qce";
>>
>> There are few issues here:
>> 1. Compatible is not documented.
>
> Its documented here:
> https://lore.kernel.org/linux-arm-msm/30756e6f-952f-ccf2-b493-e515ba4f0a64@linaro.org/
>
> [as mentioned in the dependency section in the cover letter :)]
>
>> 2. Compatible is not supported by old kernel - ABI break.
You cannot fix this with dependencies/ordering.
>> 3. Everything won't be bisectable...
>
> I think its a question of dependencies b/w the patchsets intended for
> separate areas. Let me think more on how, I can resolve it in newer
> versions.
DTS always goes separately so this also cannot be fixed with ordering or
dependencies. However if Bjorn is fine with it, it's good.
Best regards,
Krzysztof
Powered by blists - more mailing lists