Skip to contentSkip to conversation

dt-bindings: crypto: Convert ti,omap2-aes to DT schema

PATCH In review Rob Herring (Arm) 1 participant 2 messages May 13, 2025

Subsystems (2)
lore
Share & tools
lore

Rob Herring (Arm)

author maintainer
#0 lore raw

PATCH 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.

---
 .../devicetree/bindings/crypto/omap-aes.txt   | 31 ----------
 .../bindings/crypto/ti,omap4-aes.yaml         | 59 +++++++++++++++++++
 2 files changed, 59 insertions(+), 31 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/crypto/omap-aes.txt
 create mode 100644 Documentation/devicetree/bindings/crypto/ti,omap4-aes.yaml
Documentation/devicetree/bindings/crypto/omap-aes.txt deleted +0 -31
deleted file mode 100644
index fd9717653cbb..000000000000
@@ -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,omap4-aes.yaml new file +59 -0

59 lines not on this page · raw message

Signature · 1 line
2.47.2
author maintainer
#1 lore raw
Quoted 11 lines · Rob Herring (Arm)

Convert the TI OMAP AES binding to DT schema format. It's a straight forward conversion.

---
 .../devicetree/bindings/crypto/omap-aes.txt   | 31 ----------
 .../bindings/crypto/ti,omap4-aes.yaml         | 59 +++++++++++++++++++
 2 files changed, 59 insertions(+), 31 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/crypto/omap-aes.txt
 create mode 100644 Documentation/devicetree/bindings/crypto/ti,omap4-aes.yaml

My bot found errors running 'make dt_binding_check' on your patch:

yamllint warnings/errors:

dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/crypto/ti,omap4-aes.example.dtb: aes@53500000 (ti,omap4-aes): 'ti,hwmods' is a required property
from schema $id: http://devicetree.org/schemas/ti,omap4-aes.yaml#

doc reference errors (make refcheckdocs):

See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/[email protected]

The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch.

If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date:

pip3 install dtschema --upgrade

Please check and re-submit after running the above command yourself. Note that DT_SCHEMA_FILES can be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.