1*c66ec88fSEmmanuel VadotOMAP SoC AES crypto Module 2*c66ec88fSEmmanuel Vadot 3*c66ec88fSEmmanuel VadotRequired properties: 4*c66ec88fSEmmanuel Vadot 5*c66ec88fSEmmanuel Vadot- compatible : Should contain entries for this and backward compatible 6*c66ec88fSEmmanuel Vadot AES versions: 7*c66ec88fSEmmanuel Vadot - "ti,omap2-aes" for OMAP2. 8*c66ec88fSEmmanuel Vadot - "ti,omap3-aes" for OMAP3. 9*c66ec88fSEmmanuel Vadot - "ti,omap4-aes" for OMAP4 and AM33XX. 10*c66ec88fSEmmanuel Vadot Note that the OMAP2 and 3 versions are compatible (OMAP3 supports 11*c66ec88fSEmmanuel Vadot more algorithms) but they are incompatible with OMAP4. 12*c66ec88fSEmmanuel Vadot- ti,hwmods: Name of the hwmod associated with the AES module 13*c66ec88fSEmmanuel Vadot- reg : Offset and length of the register set for the module 14*c66ec88fSEmmanuel Vadot- interrupts : the interrupt-specifier for the AES module. 15*c66ec88fSEmmanuel Vadot 16*c66ec88fSEmmanuel VadotOptional properties: 17*c66ec88fSEmmanuel Vadot- dmas: DMA specifiers for tx and rx dma. See the DMA client binding, 18*c66ec88fSEmmanuel Vadot Documentation/devicetree/bindings/dma/dma.txt 19*c66ec88fSEmmanuel Vadot- dma-names: DMA request names should include "tx" and "rx" if present. 20*c66ec88fSEmmanuel Vadot 21*c66ec88fSEmmanuel VadotExample: 22*c66ec88fSEmmanuel Vadot /* AM335x */ 23*c66ec88fSEmmanuel Vadot aes: aes@53500000 { 24*c66ec88fSEmmanuel Vadot compatible = "ti,omap4-aes"; 25*c66ec88fSEmmanuel Vadot ti,hwmods = "aes"; 26*c66ec88fSEmmanuel Vadot reg = <0x53500000 0xa0>; 27*c66ec88fSEmmanuel Vadot interrupts = <102>; 28*c66ec88fSEmmanuel Vadot dmas = <&edma 6>, 29*c66ec88fSEmmanuel Vadot <&edma 5>; 30*c66ec88fSEmmanuel Vadot dma-names = "tx", "rx"; 31*c66ec88fSEmmanuel Vadot }; 32