Message ID | 20240109091708.66977-2-akhilrajeev@nvidia.com (mailing list archive) |
---|---|
State | Superseded |
Delegated to: | Herbert Xu |
Headers | show |
Series | Add Tegra Security Engine driver | expand |
On 09/01/2024 10:17, Akhil R wrote: > 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. > ... > +required: > + - compatible > + - reg > + - clocks > + - iommus > + > +additionalProperties: false > + > +examples: > + - | > + #include <dt-bindings/interrupt-controller/arm-gic.h> This does not look used. > + #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; > + }; > +... > diff --git a/Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-hash.yaml b/Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-hash.yaml > new file mode 100644 > index 000000000000..7fb32568756d > --- /dev/null > +++ b/Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-hash.yaml > @@ -0,0 +1,53 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/crypto/nvidia,tegra234-se-hash.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: NVIDIA Tegra Security Engine for HASH algorithms > + > +description: > + The Tegra Security HASH Engine accelerates the following HASH functions - > + SHA1, SHA224, SHA256, SHA384, SHA512, SHA3-224, SHA3-256, SHA3-384, SHA3-512 > + HMAC(SHA224), HMAC(SHA256), HMAC(SHA384), HMAC(SHA512) > + > +maintainers: > + - Akhil R <akhilrajeev@nvidia.com> > + > +properties: > + compatible: > + const: nvidia,tegra234-se-hash > + > + reg: > + maxItems: 1 > + > + clocks: > + maxItems: 1 > + > + iommus: > + maxItems: 1 > + > + dma-coherent: true > + > +required: > + - compatible > + - reg > + - clocks > + - iommus > + > +additionalProperties: false > + > +examples: > + - | > + #include <dt-bindings/interrupt-controller/arm-gic.h> This does not look used. > + #include <dt-bindings/memory/tegra234-mc.h> > + #include <dt-bindings/clock/tegra234-clock.h> > + With both above fixed: Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> --- This is an automated instruction, just in case, because many review tags are being ignored. If you know the process, you can skip it (please do not feel offended by me posting it here - no bad intentions intended). If you do not know the process, here is a short explanation: Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions, under or above your Signed-off-by tag. Tag is "received", when provided in a message replied to you on the mailing list. Tools like b4 can help here. However, there's no need to repost patches *only* to add the tags. The upstream maintainer will do that for tags received on the version they apply. https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577 Best regards, Krzysztof
> On 09/01/2024 10:17, Akhil R wrote: > > 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. > > > > ... > > > +required: > > + - compatible > > + - reg > > + - clocks > > + - iommus > > + > > +additionalProperties: false > > + > > +examples: > > + - | > > + #include <dt-bindings/interrupt-controller/arm-gic.h> > > This does not look used. > > > + #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; > > + }; > > +... > > diff --git a/Documentation/devicetree/bindings/crypto/nvidia,tegra234-se- > hash.yaml b/Documentation/devicetree/bindings/crypto/nvidia,tegra234-se- > hash.yaml > > new file mode 100644 > > index 000000000000..7fb32568756d > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/crypto/nvidia,tegra234-se- > hash.yaml > > @@ -0,0 +1,53 @@ > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/crypto/nvidia,tegra234-se-hash.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: NVIDIA Tegra Security Engine for HASH algorithms > > + > > +description: > > + The Tegra Security HASH Engine accelerates the following HASH functions - > > + SHA1, SHA224, SHA256, SHA384, SHA512, SHA3-224, SHA3-256, SHA3-384, > SHA3-512 > > + HMAC(SHA224), HMAC(SHA256), HMAC(SHA384), HMAC(SHA512) > > + > > +maintainers: > > + - Akhil R <akhilrajeev@nvidia.com> > > + > > +properties: > > + compatible: > > + const: nvidia,tegra234-se-hash > > + > > + reg: > > + maxItems: 1 > > + > > + clocks: > > + maxItems: 1 > > + > > + iommus: > > + maxItems: 1 > > + > > + dma-coherent: true > > + > > +required: > > + - compatible > > + - reg > > + - clocks > > + - iommus > > + > > +additionalProperties: false > > + > > +examples: > > + - | > > + #include <dt-bindings/interrupt-controller/arm-gic.h> > > This does not look used. > > > + #include <dt-bindings/memory/tegra234-mc.h> > > + #include <dt-bindings/clock/tegra234-clock.h> > > + > > With both above fixed: > > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > > --- > > This is an automated instruction, just in case, because many review tags > are being ignored. If you know the process, you can skip it (please do > not feel offended by me posting it here - no bad intentions intended). > If you do not know the process, here is a short explanation: > > Please add Acked-by/Reviewed-by/Tested-by tags when posting new > versions, under or above your Signed-off-by tag. Tag is "received", when > provided in a message replied to you on the mailing list. Tools like b4 > can help here. However, there's no need to repost patches *only* to add > the tags. The upstream maintainer will do that for tags received on the > version they apply. > > https://elixir.bootlin.com/linux/v6.5- > rc3/source/Documentation/process/submitting-patches.rst#L577 > Thanks. Noted. Will update them. Best Regards, Akhil
diff --git a/Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-aes.yaml b/Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-aes.yaml new file mode 100644 index 000000000000..206910e70ab3 --- /dev/null +++ b/Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-aes.yaml @@ -0,0 +1,53 @@ +# 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 <akhilrajeev@nvidia.com> + +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/interrupt-controller/arm-gic.h> + #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; + }; +... diff --git a/Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-hash.yaml b/Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-hash.yaml new file mode 100644 index 000000000000..7fb32568756d --- /dev/null +++ b/Documentation/devicetree/bindings/crypto/nvidia,tegra234-se-hash.yaml @@ -0,0 +1,53 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/crypto/nvidia,tegra234-se-hash.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: NVIDIA Tegra Security Engine for HASH algorithms + +description: + The Tegra Security HASH Engine accelerates the following HASH functions - + SHA1, SHA224, SHA256, SHA384, SHA512, SHA3-224, SHA3-256, SHA3-384, SHA3-512 + HMAC(SHA224), HMAC(SHA256), HMAC(SHA384), HMAC(SHA512) + +maintainers: + - Akhil R <akhilrajeev@nvidia.com> + +properties: + compatible: + const: nvidia,tegra234-se-hash + + reg: + maxItems: 1 + + clocks: + maxItems: 1 + + iommus: + maxItems: 1 + + dma-coherent: true + +required: + - compatible + - reg + - clocks + - iommus + +additionalProperties: false + +examples: + - | + #include <dt-bindings/interrupt-controller/arm-gic.h> + #include <dt-bindings/memory/tegra234-mc.h> + #include <dt-bindings/clock/tegra234-clock.h> + + crypto@15840000 { + compatible = "nvidia,tegra234-se-hash"; + reg = <0x15840000 0x10000>; + clocks = <&bpmp TEGRA234_CLK_SE>; + iommus = <&smmu TEGRA234_SID_SES_SE2>; + dma-coherent; + }; +...
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. Signed-off-by: Akhil R <akhilrajeev@nvidia.com> --- .../crypto/nvidia,tegra234-se-aes.yaml | 53 +++++++++++++++++++ .../crypto/nvidia,tegra234-se-hash.yaml | 53 +++++++++++++++++++ 2 files changed, 106 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