dt-bindings: crypto: Convert ti,omap2-aes to DT schema
Subsystems (2)
Rob Herring (Arm)
maintainerPATCH v2 1/1 dt-bindings: crypto: Convert ti,omap2-aes to DT schema
Convert the TI OMAP AES binding to DT schema format. It's a straight forward conversion.
Make "ti,hwmods" not required as it is deprecated and only used on OMAP2.
---
v2:
- Drop ti,hwmods from required
- Fix filename to be omap2, not omap4.
--- .../devicetree/bindings/crypto/omap-aes.txt | 31 ---------- .../bindings/crypto/ti,omap2-aes.yaml | 58 +++++++++++++++++++ 2 files changed, 58 insertions(+), 31 deletions(-) delete mode 100644 Documentation/devicetree/bindings/crypto/omap-aes.txt create mode 100644 Documentation/devicetree/bindings/crypto/ti,omap2-aes.yaml
Documentation/devicetree/bindings/crypto/omap-aes.txt deleted +0 -31
@@ -1,31 +0,0 @@ -OMAP SoC AES crypto Module - -Required properties: - -- compatible : Should contain entries for this and backward compatible - AES versions: - - "ti,omap2-aes" for OMAP2. - - "ti,omap3-aes" for OMAP3. - - "ti,omap4-aes" for OMAP4 and AM33XX. - Note that the OMAP2 and 3 versions are compatible (OMAP3 supports - more algorithms) but they are incompatible with OMAP4. -- ti,hwmods: Name of the hwmod associated with the AES module -- reg : Offset and length of the register set for the module -- interrupts : the interrupt-specifier for the AES module. - -Optional properties: -- dmas: DMA specifiers for tx and rx dma. See the DMA client binding, - Documentation/devicetree/bindings/dma/dma.txt -- dma-names: DMA request names should include "tx" and "rx" if present. - -Example: - /* AM335x */ - aes: aes@53500000 { - compatible = "ti,omap4-aes"; - ti,hwmods = "aes"; - reg = <0x53500000 0xa0>; - interrupts = <102>; - dmas = <&edma 6>, - <&edma 5>; - dma-names = "tx", "rx"; - };
Documentation/devicetree/bindings/crypto/ti,omap2-aes.yaml new file +58 -0
58 lines not on this page · raw message
Signature · 1 line
2.47.2
Quoted 8 lines · Rob Herring (Arm)
Convert the TI OMAP AES binding to DT schema format. It's a straight forward conversion.
Make "ti,hwmods" not required as it is deprecated and only used on OMAP2.
Signed-off-by Rob Herring (Arm) <[email protected]>---
Best regards,
Krzysztof
Herbert Xu
maintainerQuoted 11 lines · Rob Herring (Arm)
Convert the TI OMAP AES binding to DT schema format. It's a straight forward conversion.
Make "ti,hwmods" not required as it is deprecated and only used on OMAP2.
Signed-off-by Rob Herring (Arm) <[email protected]>---
v2:
- Drop ti,hwmods from required
- Fix filename to be omap2, not omap4.
Quoted 6 lines
--- .../devicetree/bindings/crypto/omap-aes.txt | 31 ---------- .../bindings/crypto/ti,omap2-aes.yaml | 58 +++++++++++++++++++ 2 files changed, 58 insertions(+), 31 deletions(-) delete mode 100644 Documentation/devicetree/bindings/crypto/omap-aes.txt create mode 100644 Documentation/devicetree/bindings/crypto/ti,omap2-aes.yaml
Patch applied. Thanks.
Signature · 3 lines
Email: Herbert Xu <[email protected]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt