Add Tegra Security Engine driver
Subsystems (6)
Akhil R
maintainerv7 cover Add Tegra Security Engine driver
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.
v6->v7:
* Move fallback_tfm and fallback_req to end of struct
* Set reqsize and statesize based on fallback_tfm
* Remove ofb(aes)v5->v6:
* Move copy/pase of intermediate results in export()/import() to 'update()' callback for CMAC as well.
* Check for rctx size when using fallback alg.
* Updated blocksizes to align with generic implementation
* Combined GCM and CCM init into aead_cra_init
* Updates to handle invalid cases better
* Reduce log levels for invalid cases to dev_dbg v4->v5:
* Move copy/paste of intermediate results in export()/import() to 'update()' callbackv3->v4:
* Remove unused header in bindings doc.
* Update commit message in host1x change.
* Fix test bot warning.v2->v3:
* Update compatible in driver and device trees.
* Remove extra new lines and symbols in binding doc. v1->v2:
* Update probe errors with 'dev_err_probe'.
* Clean up function prototypes and redundant prints.
* Remove readl/writel wrappers.
* Fix test bot warnings.
Akhil R (5):
dt-bindings: crypto: Add Tegra Security Engine
gpu: host1x: Add Tegra SE to SID table
crypto: tegra: Add Tegra Security Engine driver
arm64: defconfig: Enable Tegra Security Engine
arm64: tegra: Add Tegra Security Engine DT nodes
.../crypto/nvidia,tegra234-se-aes.yaml | 52 + .../crypto/nvidia,tegra234-se-hash.yaml | 52 + MAINTAINERS | 5 + arch/arm64/boot/dts/nvidia/tegra234.dtsi | 16 + arch/arm64/configs/defconfig | 1 + drivers/crypto/Kconfig | 8 + drivers/crypto/Makefile | 1 + drivers/crypto/tegra/Makefile | 9 + drivers/crypto/tegra/tegra-se-aes.c | 1933 +++++++++++++++++ drivers/crypto/tegra/tegra-se-hash.c | 1060 +++++++++ drivers/crypto/tegra/tegra-se-key.c | 156 ++ drivers/crypto/tegra/tegra-se-main.c | 439 ++++ drivers/crypto/tegra/tegra-se.h | 560 +++++ drivers/gpu/host1x/dev.c | 24 + 14 files changed, 4316 insertions(+) create mode 100644 Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-aes.yaml create mode 100644 Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-hash.yaml create mode 100644 drivers/crypto/tegra/Makefile create mode 100644 drivers/crypto/tegra/tegra-se-aes.c create mode 100644 drivers/crypto/tegra/tegra-se-hash.c create mode 100644 drivers/crypto/tegra/tegra-se-key.c create mode 100644 drivers/crypto/tegra/tegra-se-main.c create mode 100644 drivers/crypto/tegra/tegra-se.h
Signature · 1 line
2.43.2
Akhil R
maintainerPATCH v7 1/5 dt-bindings: crypto: Add Tegra Security Engine
Add DT binding document for Tegra Security Engine.
The AES and HASH algorithms are handled independently by separate engines within the Security Engine. These engines are registered as two separate crypto engine drivers.
--- .../crypto/nvidia,tegra234-se-aes.yaml | 52 +++++++++++++++++++ .../crypto/nvidia,tegra234-se-hash.yaml | 52 +++++++++++++++++++ 2 files changed, 104 insertions(+) create mode 100644 Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-aes.yaml create mode 100644 Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-hash.yaml
Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-aes.yaml new file +52 -0
@@ -0,0 +1,52 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/crypto/nvidia,tegra234-se-aes.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: NVIDIA Tegra Security Engine for AES algorithms + +description: + The Tegra Security Engine accelerates the following AES encryption/decryption + algorithms - AES-ECB, AES-CBC, AES-OFB, AES-XTS, AES-CTR, AES-GCM, AES-CCM, + AES-CMAC + +maintainers: + - Akhil R <[email protected]> + +properties: + compatible: + const: nvidia,tegra234-se-aes + + reg: + maxItems: 1 + + clocks: + maxItems: 1 + + iommus: + maxItems: 1 + + dma-coherent: true + +required: + - compatible + - reg + - clocks + - iommus + +additionalProperties: false + +examples: + - | + #include <dt-bindings/memory/tegra234-mc.h> + #include <dt-bindings/clock/tegra234-clock.h> + + crypto@15820000 { + compatible = "nvidia,tegra234-se-aes"; + reg = <0x15820000 0x10000>; + clocks = <&bpmp TEGRA234_CLK_SE>; + iommus = <&smmu TEGRA234_SID_SES_SE1>; + dma-coherent; + }; +...
Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-hash.yaml new file +52 -0
52 lines not on this page · raw message
Signature · 1 line
2.43.2
Akhil R
maintainerPATCH v7 2/5 gpu: host1x: Add Tegra SE to SID table
In reply to Akhil RAdd Tegra Security Engine details to the SID table in host1x driver. These entries are required to be in place to configure the stream ID for SE. Register writes to stream ID registers fail otherwise.
--- drivers/gpu/host1x/dev.c | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+)
drivers/gpu/host1x/dev.c +24 -0
@@ -215,6 +215,30 @@ static const struct host1x_info host1x07_info = {* and firmware stream ID in the MMIO path table. */ static const struct host1x_sid_entry tegra234_sid_table[] = { + { +/* SE2 MMIO */ + .base =0x1658 , + .offset =0x90 , + .limit =0x90 + }, + { +/* SE4 MMIO */ + .base =0x1660 , + .offset =0x90 , + .limit =0x90 + }, + { +/* SE2 channel */ + .base =0x1738 , + .offset =0x90 , + .limit =0x90 + }, + { +/* SE4 channel */ + .base =0x1740 , + .offset =0x90 , + .limit =0x90 + }, {/* VIC channel */ .base =0x17b8 ,
Signature · 1 line
2.43.2
Akhil R
maintainerPATCH v7 3/5 crypto: tegra: Add Tegra Security Engine driver
In reply to Akhil RAdd support for Tegra Security Engine which can accelerate 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.
--- MAINTAINERS | 5 + drivers/crypto/Kconfig | 8 + drivers/crypto/Makefile | 1 + drivers/crypto/tegra/Makefile | 9 + drivers/crypto/tegra/tegra-se-aes.c | 1933 ++++++++++++++++++++++++++ drivers/crypto/tegra/tegra-se-hash.c | 1060 ++++++++++++++ drivers/crypto/tegra/tegra-se-key.c | 156 +++ drivers/crypto/tegra/tegra-se-main.c | 439 ++++++ drivers/crypto/tegra/tegra-se.h | 560 ++++++++ 9 files changed, 4171 insertions(+) create mode 100644 drivers/crypto/tegra/Makefile create mode 100644 drivers/crypto/tegra/tegra-se-aes.c create mode 100644 drivers/crypto/tegra/tegra-se-hash.c create mode 100644 drivers/crypto/tegra/tegra-se-key.c create mode 100644 drivers/crypto/tegra/tegra-se-main.c create mode 100644 drivers/crypto/tegra/tegra-se.h
MAINTAINERS +5 -0
@@ -21702,6 +21702,11 @@ M: Prashant Gaikwad <[email protected]> S: Supported F: drivers/clk/tegra/ +TEGRA CRYPTO DRIVERS +M: Akhil R <[email protected]> +S: Supported +F: drivers/crypto/tegra/* + TEGRA DMA DRIVERS M: Laxman Dewangan <[email protected]> M: Jon Hunter <[email protected]>
drivers/crypto/Kconfig +8 -0
@@ -660,6 +660,14 @@ config CRYPTO_DEV_ROCKCHIP_DEBUG This will create /sys/kernel/debug/rk3288_crypto/stats for displaying the number of requests per algorithm and other internal stats. +config CRYPTO_DEV_TEGRA + tristate "Enable Tegra Security Engine" + depends on TEGRA_HOST1X + select CRYPTO_ENGINE + + help + Select this to enable Tegra Security Engine which accelerates various + AES encryption/decryption and HASH algorithms. config CRYPTO_DEV_ZYNQMP_AES tristate "Support for Xilinx ZynqMP AES hw accelerator"
drivers/crypto/Makefile +1 -0
@@ -41,6 +41,7 @@ obj-$(CONFIG_CRYPTO_DEV_SAHARA) += sahara.o obj-$(CONFIG_CRYPTO_DEV_SL3516) += gemini/ obj-y += stm32/ obj-$(CONFIG_CRYPTO_DEV_TALITOS) += talitos.o +obj-$(CONFIG_CRYPTO_DEV_TEGRA) += tegra/ obj-$(CONFIG_CRYPTO_DEV_VIRTIO) += virtio/ #obj-$(CONFIG_CRYPTO_DEV_VMX) += vmx/ obj-$(CONFIG_CRYPTO_DEV_BCM_SPU) += bcm/
drivers/crypto/tegra/Makefile new file +9 -0
@@ -0,0 +1,9 @@ +// SPDX-License-Identifier: GPL-2.0-only +// SPDX-FileCopyrightText: Copyright (c) 2023 NVIDIA CORPORATION & AFFILIATES. All rights reserved. + +tegra-se-objs := tegra-se-key.o tegra-se-main.o + +tegra-se-y += tegra-se-aes.o +tegra-se-y += tegra-se-hash.o + +obj-$(CONFIG_CRYPTO_DEV_TEGRA) += tegra-se.o
drivers/crypto/tegra/tegra-se-aes.c new file +1933 -0
1,933 lines not on this page · raw message
drivers/crypto/tegra/tegra-se-hash.c new file +1060 -0
1,026 lines not on this page · raw message
drivers/crypto/tegra/tegra-se-key.c new file +156 -0
156 lines not on this page · raw message
drivers/crypto/tegra/tegra-se-main.c new file +439 -0
439 lines not on this page · raw message
drivers/crypto/tegra/tegra-se.h new file +560 -0
560 lines not on this page · raw message
The rest of this diff is not shown. View the raw message.
Signature · 1 line
2.43.2
Part of the diff is not shown here. View the raw message.
Akhil R
maintainerPATCH v7 4/5 arm64: defconfig: Enable Tegra Security Engine
In reply to Akhil REnable Tegra Security Engine which can accelerate various AES and HASH algorithms on supported hardware.
--- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+)
arch/arm64/configs/defconfig +1 -0
@@ -1647,6 +1647,7 @@ CONFIG_CRYPTO_DEV_FSL_CAAM=m CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=m CONFIG_CRYPTO_DEV_QCE=m CONFIG_CRYPTO_DEV_QCOM_RNG=m +CONFIG_CRYPTO_DEV_TEGRA=m CONFIG_CRYPTO_DEV_CCREE=m CONFIG_CRYPTO_DEV_HISI_SEC2=m CONFIG_CRYPTO_DEV_HISI_ZIP=m
Signature · 1 line
2.43.2
Akhil R
maintainerPATCH v7 5/5 arm64: tegra: Add Tegra Security Engine DT nodes
In reply to Akhil RAdd device tree nodes for Tegra AES and HASH engines.
--- arch/arm64/boot/dts/nvidia/tegra234.dtsi | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)
arch/arm64/boot/dts/nvidia/tegra234.dtsi +16 -0
@@ -4406,6 +4406,22 @@ nvdec@15480000 { */ status = "disabled"; }; + + crypto@15820000 { + compatible = "nvidia,tegra234-se-aes"; + reg = <0x00 0x15820000 0x00 0x10000>; + clocks = <&bpmp TEGRA234_CLK_SE>; + iommus = <&smmu_niso1 TEGRA234_SID_SES_SE1>; + dma-coherent; + }; + + crypto@15840000 { + compatible = "nvidia,tegra234-se-hash"; + reg = <0x00 0x15840000 0x00 0x10000>; + clocks = <&bpmp TEGRA234_CLK_SE>; + iommus = <&smmu_niso1 TEGRA234_SID_SES_SE2>; + dma-coherent; + }; }; pcie@140a0000 {
Signature · 1 line
2.43.2
Herbert Xu
maintainerQuoted 60 lines · Akhil R
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.
v6->v7:
* Movefallback_tfmandfallback_reqto end of struct
* Set reqsize and statesize based onfallback_tfm
* Remove ofb(aes)v5->v6:
* Move copy/pase of intermediate results in export()/import() to 'update()' callback for CMAC as well.
* Check for rctx size when using fallback alg.
* Updated blocksizes to align with generic implementation
* Combined GCM and CCM init intoaead_cra_init
* Updates to handle invalid cases better
* Reduce log levels for invalid cases todev_dbgv4->v5:
* Move copy/paste of intermediate results in export()/import() to 'update()' callbackv3->v4:
* Remove unused header in bindings doc.
* Update commit message in host1x change.
* Fix test bot warning.v2->v3:
* Update compatible in driver and device trees.
* Remove extra new lines and symbols in binding doc.v1->v2:
* Update probe errors with 'dev_err_probe'.
* Clean up function prototypes and redundant prints.
* Remove readl/writel wrappers.
* Fix test bot warnings.Akhil R (5):
dt-bindings: crypto: Add Tegra Security Engine
gpu: host1x: Add Tegra SE to SID table
crypto: tegra: Add Tegra Security Engine driver
arm64: defconfig: Enable Tegra Security Engine
arm64: tegra: Add Tegra Security Engine DT nodes.../crypto/nvidia,tegra234-se-aes.yaml | 52 + .../crypto/nvidia,tegra234-se-hash.yaml | 52 + MAINTAINERS | 5 + arch/arm64/boot/dts/nvidia/tegra234.dtsi | 16 + arch/arm64/configs/defconfig | 1 + drivers/crypto/Kconfig | 8 + drivers/crypto/Makefile | 1 + drivers/crypto/tegra/Makefile | 9 + drivers/crypto/tegra/tegra-se-aes.c | 1933 +++++++++++++++++ drivers/crypto/tegra/tegra-se-hash.c | 1060 +++++++++ drivers/crypto/tegra/tegra-se-key.c | 156 ++ drivers/crypto/tegra/tegra-se-main.c | 439 ++++ drivers/crypto/tegra/tegra-se.h | 560 +++++ drivers/gpu/host1x/dev.c | 24 + 14 files changed, 4316 insertions(+)
Quoted 11 lines
create mode 100644 Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-aes.yaml create mode 100644 Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-hash.yaml create mode 100644 drivers/crypto/tegra/Makefile create mode 100644 drivers/crypto/tegra/tegra-se-aes.c create mode 100644 drivers/crypto/tegra/tegra-se-hash.c create mode 100644 drivers/crypto/tegra/tegra-se-key.c create mode 100644 drivers/crypto/tegra/tegra-se-main.c create mode 100644 drivers/crypto/tegra/tegra-se.hSignature · 1 line
2.43.2
All applied. Thanks.
Signature · 3 lines
Email: Herbert Xu <[email protected]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Akhil R
maintainerQuoted 73 lines · Akhil R
Quoted 72 lines
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.
v6->v7:
* Movefallback_tfmandfallback_reqto end of struct
* Set reqsize and statesize based onfallback_tfm
* Remove ofb(aes)v5->v6:
* Move copy/pase of intermediate results in export()/import() to 'update()' callback for CMAC as well.
* Check for rctx size when using fallback alg.
* Updated blocksizes to align with generic implementation
* Combined GCM and CCM init intoaead_cra_init
* Updates to handle invalid cases better
* Reduce log levels for invalid cases todev_dbgv4->v5:
* Move copy/paste of intermediate results in export()/import() to 'update()' callbackv3->v4:
* Remove unused header in bindings doc.
* Update commit message in host1x change.
* Fix test bot warning.v2->v3:
* Update compatible in driver and device trees.
* Remove extra new lines and symbols in binding doc.v1->v2:
* Update probe errors with 'dev_err_probe'.
* Clean up function prototypes and redundant prints.
* Remove readl/writel wrappers.
* Fix test bot warnings.Akhil R (5):
dt-bindings: crypto: Add Tegra Security Engine
gpu: host1x: Add Tegra SE to SID table
crypto: tegra: Add Tegra Security Engine driver
arm64: defconfig: Enable Tegra Security Engine
arm64: tegra: Add Tegra Security Engine DT nodes.../crypto/nvidia,tegra234-se-aes.yaml | 52 + .../crypto/nvidia,tegra234-se-hash.yaml | 52 + MAINTAINERS | 5 + arch/arm64/boot/dts/nvidia/tegra234.dtsi | 16 + arch/arm64/configs/defconfig | 1 + drivers/crypto/Kconfig | 8 + drivers/crypto/Makefile | 1 + drivers/crypto/tegra/Makefile | 9 + drivers/crypto/tegra/tegra-se-aes.c | 1933 +++++++++++++++++ drivers/crypto/tegra/tegra-se-hash.c | 1060 +++++++++ drivers/crypto/tegra/tegra-se-key.c | 156 ++ drivers/crypto/tegra/tegra-se-main.c | 439 ++++ drivers/crypto/tegra/tegra-se.h | 560 +++++ drivers/gpu/host1x/dev.c | 24 + 14 files changed, 4316 insertions(+) create mode 100644 Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-aes.yaml create mode 100644 Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-hash.yaml create mode 100644 drivers/crypto/tegra/Makefile create mode 100644 drivers/crypto/tegra/tegra-se-aes.c create mode 100644 drivers/crypto/tegra/tegra-se-hash.c create mode 100644 drivers/crypto/tegra/tegra-se-key.c create mode 100644 drivers/crypto/tegra/tegra-se-main.c create mode 100644 drivers/crypto/tegra/tegra-se.h
Quoted 4 lines
Quoted 2 lines
--
2.43.2All applied. Thanks.
Hi Herbert,
Thanks for applying the patches. I see that the driver is in -next now.
I had a question based on some of our customer feedback with this driver. While running tcrypt mode=10 with Tegra SE driver, it shows errors for lrw(aes), rfc3686(ctr(aes)) etc. which it does not support.
I was wondering if there is an option to skip unsupported algorithms in the Tcrypt test. I don't see any vendor specific test modes in tcrypt as well. Could you share any suggestion on the best way to handle this? Or is this an expected output of the test?
Thanks and Regards,
Akhil
Herbert Xu
maintainerQuoted 4 lines · Akhil R
I had a question based on some of our customer feedback with this driver. While running tcrypt mode=10 with Tegra SE driver, it shows errors for lrw(aes), rfc3686(ctr(aes)) etc. which it does not support.
Algorithms that are not supported by your driver should automatically be routed to software implementations. What errors are you getting?
Cheers,
Signature · 3 lines
Email: Herbert Xu <[email protected]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Akhil R
maintainerQuoted 8 lines · Akhil R
Quoted 4 lines
I had a question based on some of our customer feedback with this driver. While running tcrypt mode=10 with Tegra SE driver, it shows errors for lrw(aes), rfc3686(ctr(aes)) etc. which it does not support.
Algorithms that are not supported by your driver should automatically be routed to software implementations. What errors are you getting?
I get the below error. But this is because we don't have CONFIG_LRW enabled in our defconfig.
[ 1240.771301] alg: skcipher: failed to allocate transform for lrw(aes): -2 [ 1240.778308] alg: self-tests for lrw(aes) using lrw(aes) failed (rc=-2)
So, I suppose enabling the defconfig is the right and only fix here?
Thanks and Regards,
Akhil
Jon Hunter
maintainerQuoted 8 lines · Akhil R
Quoted 8 lines · Akhil R
Quoted 4 lines
I had a question based on some of our customer feedback with this driver. While running tcrypt mode=10 with Tegra SE driver, it shows errors for lrw(aes), rfc3686(ctr(aes)) etc. which it does not support.
Algorithms that are not supported by your driver should automatically be routed to software implementations. What errors are you getting?
Quoted 7 lines
I get the below error. But this is because we don't have
CONFIG_LRWenabled in our defconfig.[ 1240.771301] alg: skcipher: failed to allocate transform for lrw(aes): -2 [ 1240.778308] alg: self-tests for lrw(aes) using lrw(aes) failed (rc=-2)So, I suppose enabling the defconfig is the right and only fix here?
Should we be selecting for option for Tegra so there is a clear dependency?
Jon
Signature · 1 line
nvpublic
Herbert Xu
maintainerQuoted 8 lines · Akhil R
I get the below error. But this is because we don't have
CONFIG_LRWenabled in our defconfig.[ 1240.771301] alg: skcipher: failed to allocate transform for lrw(aes): -2 [ 1240.778308] alg: self-tests for lrw(aes) using lrw(aes) failed (rc=-2)So, I suppose enabling the defconfig is the right and only fix here?
You're not supposed to be using tcrypt to test drivers. The driver will be tested automatically upon registration.
The tcrypt module is vestigial.
Cheers,
Signature · 3 lines
Email: Herbert Xu <[email protected]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Akhil R
maintainerQuoted 8 lines · Akhil R
Quoted 7 lines
I get the below error. But this is because we don't have
CONFIG_LRWenabled in our defconfig.[ 1240.771301] alg: skcipher: failed to allocate transform for lrw(aes): -2 [ 1240.778308] alg: self-tests for lrw(aes) using lrw(aes) failed (rc=-2)
Quoted 7 lines
Quoted 1 line
So, I suppose enabling the defconfig is the right and only fix here?
You're not supposed to be using tcrypt to test drivers. The driver will be tested automatically upon registration.
The tcrypt module is vestigial.
Oh. Okay. Got it - makes sense.
Thanks for clarifying.
Regards,
Akhil
Thierry Reding
AppliedRe: (subset) [PATCH v7 0/5] Add Tegra Security Engine driver
In reply to Akhil RFrom: Thierry Reding <[email protected]>
Quoted 10 lines · Akhil R
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
Best regards,
Signature · 1 line
Thierry Reding <[email protected]>
Re: (subset) [PATCH v7 0/5] Add Tegra Security Engine driver
Quoted 13 lines · Thierry Reding
From: Thierry Reding <[email protected]>
Quoted 9 lines · Akhil R
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.
Quoted 6 lines
Quoted 1 line
[...]
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