xref: /freebsd/sys/contrib/device-tree/Bindings/crypto/marvell-cesa.txt (revision dd41de95a84d979615a2ef11df6850622bf6184e)
1Marvell Cryptographic Engines And Security Accelerator
2
3Required properties:
4- compatible: should be one of the following string
5	      "marvell,orion-crypto"
6	      "marvell,kirkwood-crypto"
7	      "marvell,dove-crypto"
8	      "marvell,armada-370-crypto"
9	      "marvell,armada-xp-crypto"
10	      "marvell,armada-375-crypto"
11	      "marvell,armada-38x-crypto"
12- reg: base physical address of the engine and length of memory mapped
13       region. Can also contain an entry for the SRAM attached to the CESA,
14       but this representation is deprecated and marvell,crypto-srams should
15       be used instead
16- reg-names: "regs". Can contain an "sram" entry, but this representation
17	     is deprecated and marvell,crypto-srams should be used instead
18- interrupts: interrupt number
19- clocks: reference to the crypto engines clocks. This property is not
20	  required for orion and kirkwood platforms
21- clock-names: "cesaX" and "cesazX", X should be replaced by the crypto engine
22	       id.
23	       This property is not required for the orion and kirkwoord
24	       platforms.
25	       "cesazX" clocks are not required on armada-370 platforms
26- marvell,crypto-srams: phandle to crypto SRAM definitions
27
28Optional properties:
29- marvell,crypto-sram-size: SRAM size reserved for crypto operations, if not
30			    specified the whole SRAM is used (2KB)
31
32
33Examples:
34
35	crypto@90000 {
36		compatible = "marvell,armada-xp-crypto";
37		reg = <0x90000 0x10000>;
38		reg-names = "regs";
39		interrupts = <48>, <49>;
40		clocks = <&gateclk 23>, <&gateclk 23>;
41		clock-names = "cesa0", "cesa1";
42		marvell,crypto-srams = <&crypto_sram0>, <&crypto_sram1>;
43		marvell,crypto-sram-size = <0x600>;
44	};
45