From: "Thierry Reding" <thierry.reding@gmail.com>
To: "Thierry Reding" <thierry.reding@gmail.com>,
<herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<robh@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <jonathanh@nvidia.com>,
<catalin.marinas@arm.com>, <will@kernel.org>,
<mperttunen@nvidia.com>, <airlied@gmail.com>, <daniel@ffwll.ch>,
<linux-crypto@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<dri-devel@lists.freedesktop.org>,
"Akhil R" <akhilrajeev@nvidia.com>
Subject: Re: (subset) [PATCH v7 0/5] Add Tegra Security Engine driver
Date: Fri, 26 Apr 2024 17:35:42 +0200 [thread overview]
Message-ID: <D0U5YAWTAEXO.1GLSZDY2XKKRV@gmail.com> (raw)
In-Reply-To: <171414552137.2298337.4837480787385115790.b4-ty@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Fri Apr 26, 2024 at 5:32 PM CEST, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
>
> On Wed, 03 Apr 2024 15:30:34 +0530, Akhil R wrote:
> > Add support for Tegra Security Engine which can accelerates various
> > crypto algorithms. The Engine has two separate instances within for
> > AES and HASH algorithms respectively.
> >
> > The driver registers two crypto engines - one for AES and another for
> > HASH algorithms and these operate independently and both uses the host1x
> > bus. Additionally, it provides hardware-assisted key protection for up to
> > 15 symmetric keys which it can use for the cipher operations.
> >
> > [...]
>
> Applied, thanks!
>
> [4/5] arm64: defconfig: Enable Tegra Security Engine
> commit: 4d4d3fe6b3cc2a0b2a334a08bb9c64ba1dcbbea4
For the record, I've also applied patch 5/5 but it didn't apply cleanly
and so b4 didn't track it properly.
Thanks,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-04-26 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 10:00 [PATCH v7 0/5] Add Tegra Security Engine driver Akhil R
2024-04-03 10:00 ` [PATCH v7 1/5] dt-bindings: crypto: Add Tegra Security Engine Akhil R
2024-04-03 10:00 ` [PATCH v7 2/5] gpu: host1x: Add Tegra SE to SID table Akhil R
2024-04-03 10:00 ` [PATCH v7 3/5] crypto: tegra: Add Tegra Security Engine driver Akhil R
2024-04-03 10:00 ` [PATCH v7 4/5] arm64: defconfig: Enable Tegra Security Engine Akhil R
2024-04-03 10:00 ` [PATCH v7 5/5] arm64: tegra: Add Tegra Security Engine DT nodes Akhil R
2024-04-12 7:31 ` [PATCH v7 0/5] Add Tegra Security Engine driver Herbert Xu
2024-04-26 15:32 ` (subset) " Thierry Reding
2024-04-26 15:35 ` Thierry Reding [this message]
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=D0U5YAWTAEXO.1GLSZDY2XKKRV@gmail.com \
--to=thierry.reding@gmail.com \
--cc=airlied@gmail.com \
--cc=akhilrajeev@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=herbert@gondor.apana.org.au \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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@kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).