[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <662833e4-fd2a-481c-9d40-5e691d9a0cfa@linaro.org>
Date: Thu, 28 Dec 2023 11:29:38 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Akhil R <akhilrajeev@...dia.com>,
"herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>,
"davem@...emloft.net" <davem@...emloft.net>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"krzysztof.kozlowski+dt@...aro.org" <krzysztof.kozlowski+dt@...aro.org>,
"conor+dt@...nel.org" <conor+dt@...nel.org>,
"thierry.reding@...il.com" <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"will@...nel.org" <will@...nel.org>, Mikko Perttunen
<mperttunen@...dia.com>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"krzk@...nel.org" <krzk@...nel.org>
Subject: Re: [PATCH v2 1/5] dt-bindings: crypto: Add Tegra Security Engine
On 28/12/2023 10:33, Akhil R wrote:
>>> +properties:
>>> + compatible:
>>> + const: nvidia,tegra234-se4-hash
>>
>> What is se4?
>>
>> Anyway, filename like compatible.
> Similar to the above, the hardware name is SE4.
>
> nvidia,tegra234-se-aes and nvidia,tegra234-se-hash does look good to me. But I am a bit concerned
> about the ABI breakage in case, we need a different compatible for the remaining instance.
Isn't this a new device? What ABI breakage? What would be affected?
Best regards,
Krzysztof
Powered by blists - more mailing lists