crypto: brcm - DT documentation for Broadcom SPU hardware
authorRob Rice <rob.rice@broadcom.com>
Fri, 3 Feb 2017 17:55:32 +0000 (12:55 -0500)
committerHerbert Xu <herbert@gondor.apana.org.au>
Sat, 11 Feb 2017 09:55:19 +0000 (17:55 +0800)
Device tree documentation for Broadcom Secure Processing Unit
(SPU) crypto hardware.

Signed-off-by: Steve Lin <steven.lin1@broadcom.com>
Signed-off-by: Rob Rice <rob.rice@broadcom.com>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Documentation/devicetree/bindings/crypto/brcm,spu-crypto.txt [new file with mode: 0644]

diff --git a/Documentation/devicetree/bindings/crypto/brcm,spu-crypto.txt b/Documentation/devicetree/bindings/crypto/brcm,spu-crypto.txt
new file mode 100644 (file)
index 0000000..29b6007
--- /dev/null
@@ -0,0 +1,22 @@
+The Broadcom Secure Processing Unit (SPU) hardware supports symmetric
+cryptographic offload for Broadcom SoCs. A SoC may have multiple SPU hardware
+blocks.
+
+Required properties:
+- compatible: Should be one of the following:
+  brcm,spum-crypto - for devices with SPU-M hardware
+  brcm,spu2-crypto - for devices with SPU2 hardware
+  brcm,spu2-v2-crypto - for devices with enhanced SPU2 hardware features like SHA3
+  and Rabin Fingerprint support
+  brcm,spum-nsp-crypto - for the Northstar Plus variant of the SPU-M hardware
+
+- reg: Should contain SPU registers location and length.
+- mboxes: The mailbox channel to be used to communicate with the SPU.
+  Mailbox channels correspond to DMA rings on the device.
+
+Example:
+       crypto@612d0000 {
+               compatible = "brcm,spum-crypto";
+               reg = <0 0x612d0000 0 0x900>;
+               mboxes = <&pdc0 0>;
+       };