| Message ID | 1480714499-1476-2-git-send-email-rob.rice@broadcom.com |
|---|---|
| State | Changes Requested, archived |
| Headers | show |
On Fri, Dec 02, 2016 at 04:34:57PM -0500, Rob Rice wrote: > Device tree documentation for Broadcom Secure Processing Unit > (SPU) crypto driver. > > Signed-off-by: Steve Lin <steven.lin1@broadcom.com> > Signed-off-by: Rob Rice <rob.rice@broadcom.com> > --- > .../devicetree/bindings/crypto/brcm,spu-crypto.txt | 25 ++++++++++++++++++++++ > 1 file changed, 25 insertions(+) > create mode 100644 Documentation/devicetree/bindings/crypto/brcm,spu-crypto.txt > > diff --git a/Documentation/devicetree/bindings/crypto/brcm,spu-crypto.txt b/Documentation/devicetree/bindings/crypto/brcm,spu-crypto.txt > new file mode 100644 > index 0000000..e5fe942 > --- /dev/null > +++ b/Documentation/devicetree/bindings/crypto/brcm,spu-crypto.txt > @@ -0,0 +1,25 @@ > +The Broadcom Secure Processing Unit (SPU) driver supports symmetric Bindings describe h/w, not drivers. > +cryptographic offload for Broadcom SoCs with SPU hardware. A SoC may have > +multiple SPU hardware blocks. > + > +Required properties: > +- compatible : Should be "brcm,spum-crypto" for devices with SPU-M hardware Additionally, you should have SoC specific compatible here. > + (e.g., Northstar2) or "brcm,spum-nsp-crypto" for the Northstar Plus variant > + of the SPU-M hardware. > + > +- reg: Should contain SPU registers location and length. > +- mboxes: A list of mailbox channels to be used by the kernel driver. Mailbox > +channels correspond to DMA rings on the device. What determines the mbox assignment? Needs to specify how many. > + > +Example: > + spu-crypto@612d0000 { Just crypto@... Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/crypto/brcm,spu-crypto.txt b/Documentation/devicetree/bindings/crypto/brcm,spu-crypto.txt new file mode 100644 index 0000000..e5fe942 --- /dev/null +++ b/Documentation/devicetree/bindings/crypto/brcm,spu-crypto.txt @@ -0,0 +1,25 @@ +The Broadcom Secure Processing Unit (SPU) driver supports symmetric +cryptographic offload for Broadcom SoCs with SPU hardware. A SoC may have +multiple SPU hardware blocks. + +Required properties: +- compatible : Should be "brcm,spum-crypto" for devices with SPU-M hardware + (e.g., Northstar2) or "brcm,spum-nsp-crypto" for the Northstar Plus variant + of the SPU-M hardware. + +- reg: Should contain SPU registers location and length. +- mboxes: A list of mailbox channels to be used by the kernel driver. Mailbox +channels correspond to DMA rings on the device. + +Example: + spu-crypto@612d0000 { + compatible = "brcm,spum-crypto"; + reg = <0 0x612d0000 0 0x900>, /* SPU 0 control regs */ + <0 0x612f0000 0 0x900>, /* SPU 1 control regs */ + <0 0x61310000 0 0x900>, /* SPU 2 control regs */ + <0 0x61330000 0 0x900>; /* SPU 3 control regs */ + mboxes = <&pdc0 0>, + <&pdc1 0>, + <&pdc2 0>, + <&pdc3 0>; + };