Path: blob/main/sys/contrib/device-tree/Bindings/crypto/marvell-cesa.txt
48375 views
Marvell Cryptographic Engines And Security Accelerator12Required properties:3- compatible: should be one of the following string4"marvell,orion-crypto"5"marvell,kirkwood-crypto"6"marvell,dove-crypto"7"marvell,armada-370-crypto"8"marvell,armada-xp-crypto"9"marvell,armada-375-crypto"10"marvell,armada-38x-crypto"11- reg: base physical address of the engine and length of memory mapped12region. Can also contain an entry for the SRAM attached to the CESA,13but this representation is deprecated and marvell,crypto-srams should14be used instead15- reg-names: "regs". Can contain an "sram" entry, but this representation16is deprecated and marvell,crypto-srams should be used instead17- interrupts: interrupt number18- clocks: reference to the crypto engines clocks. This property is not19required for orion and kirkwood platforms20- clock-names: "cesaX" and "cesazX", X should be replaced by the crypto engine21id.22This property is not required for the orion and kirkwoord23platforms.24"cesazX" clocks are not required on armada-370 platforms25- marvell,crypto-srams: phandle to crypto SRAM definitions2627Optional properties:28- marvell,crypto-sram-size: SRAM size reserved for crypto operations, if not29specified the whole SRAM is used (2KB)303132Examples:3334crypto@90000 {35compatible = "marvell,armada-xp-crypto";36reg = <0x90000 0x10000>;37reg-names = "regs";38interrupts = <48>, <49>;39clocks = <&gateclk 23>, <&gateclk 23>;40clock-names = "cesa0", "cesa1";41marvell,crypto-srams = <&crypto_sram0>, <&crypto_sram1>;42marvell,crypto-sram-size = <0x600>;43};444546