[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37782447-43c7-50f9-b9b4-5fbca94ce8c6@linaro.org>
Date: Thu, 10 Aug 2023 08:22:13 +0100
From: Tudor Ambarus <tudor.ambarus@...aro.org>
To: Varshini.Rajendran@...rochip.com, herbert@...dor.apana.org.au,
davem@...emloft.net, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
Nicolas.Ferre@...rochip.com, alexandre.belloni@...tlin.com,
claudiu.beznea@...rochip.com, linux-crypto@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 11/50] dt-bindings: crypto: add sam9x7 in Atmel TDES
On 8/10/23 06:38, Varshini.Rajendran@...rochip.com wrote:
>> On 7/28/23 11:24, Varshini Rajendran wrote:
>>> Add DT bindings for atmel TDES.
>> NACK. The atmel crypto drivers check the version at runtime and
>> fill a capabilities structure based on the version identified.
>> There's a single compatible regardless of the version of the IP
>> used until now, why do you want to change it?
>>
> Hi Tudor,
Hi,
>
> I am aware that there is no change in the crypto IP used. This patch is
> to add a SoC specific compatible as expected by writing-bindings
> guideline. Maybe a bit more explanation in the commit description might
> do the trick.
>
So you add a compatible that will never be used just to comply with
the writing bindings guideline?
Powered by blists - more mailing lists