From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Akhil R <akhilrajeev@nvidia.com>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
Mikko Perttunen <mperttunen@nvidia.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"krzk@kernel.org" <krzk@kernel.org>
Subject: Re: [PATCH v2 1/5] dt-bindings: crypto: Add Tegra Security Engine
Date: Thu, 28 Dec 2023 11:29:38 +0100 [thread overview]
Message-ID: <662833e4-fd2a-481c-9d40-5e691d9a0cfa@linaro.org> (raw)
In-Reply-To: <SJ1PR12MB63397127C6E6D1289FA7E464C09EA@SJ1PR12MB6339.namprd12.prod.outlook.com>
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
next prev parent reply other threads:[~2023-12-28 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 12:56 [PATCH v2 0/5] Add Tegra Security Engine driver Akhil R
2023-12-19 12:56 ` [PATCH v2 1/5] dt-bindings: crypto: Add Tegra Security Engine Akhil R
2023-12-20 15:44 ` Krzysztof Kozlowski
2023-12-28 9:33 ` Akhil R
2023-12-28 10:29 ` Krzysztof Kozlowski [this message]
2023-12-29 7:11 ` Akhil R
2023-12-30 14:21 ` Krzysztof Kozlowski
2024-01-02 4:27 ` Akhil R
2023-12-19 12:56 ` [PATCH v2 2/5] gpu: host1x: Add Tegra SE to SID table Akhil R
2023-12-19 12:56 ` [PATCH v2 3/5] crypto: tegra: Add Tegra Security Engine driver Akhil R
2023-12-19 12:56 ` [PATCH v2 4/5] arm64: defconfig: Enable Tegra Security Engine Akhil R
2023-12-19 12:56 ` [PATCH v2 5/5] arm64: tegra: Add Tegra Security Engine DT nodes Akhil R
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=662833e4-fd2a-481c-9d40-5e691d9a0cfa@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=akhilrajeev@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jonathanh@nvidia.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).