Skip to contentSkip to conversation

dt-bindings: crypto: Convert ti,omap4-des to DT schema

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

Subsystems (2)

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore

Rob Herring (Arm)

author maintainer
#0 lore raw

PATCH 1/1 dt-bindings: crypto: Convert ti,omap4-des to DT schema

Convert the TI OMAP DES binding to DT schema format.

Drop "ti,hwmods" as it is not actually used for this binding. Only OMAP2 platforms are using it.

---
 .../devicetree/bindings/crypto/omap-des.txt   | 30 ---------
 .../bindings/crypto/ti,omap4-des.yaml         | 66 +++++++++++++++++++
 2 files changed, 66 insertions(+), 30 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/crypto/omap-des.txt
 create mode 100644 Documentation/devicetree/bindings/crypto/ti,omap4-des.yaml
Documentation/devicetree/bindings/crypto/omap-des.txt deleted +0 -30
deleted file mode 100644
index e8c63bf2e16d..000000000000
@@ -1,30 +0,0 @@
-OMAP SoC DES crypto Module
-
-Required properties:
-
-- compatible : Should contain "ti,omap4-des"
-- ti,hwmods: Name of the hwmod associated with the DES module
-- reg : Offset and length of the register set for the module
-- interrupts : the interrupt-specifier for the DES module
-- clocks : A phandle to the functional clock node of the DES module
-           corresponding to each entry in clock-names
-- clock-names : Name of the functional clock, should be "fck"
-
-Optional properties:
-- dmas: DMA specifiers for tx and rx dma. See the DMA client binding,
-	Documentation/devicetree/bindings/dma/dma.txt
-	Each entry corresponds to an entry in dma-names
-- dma-names: DMA request names should include "tx" and "rx" if present
-
-Example:
-	/* DRA7xx SoC */
-	des: des@480a5000 {
-		compatible = "ti,omap4-des";
-		ti,hwmods = "des";
-		reg = <0x480a5000 0xa0>;
-		interrupts = <GIC_SPI 82 IRQ_TYPE_LEVEL_HIGH>;
-		dmas = <&sdma 117>, <&sdma 116>;
-		dma-names = "tx", "rx";
-		clocks = <&l3_iclk_div>;
-		clock-names = "fck";
-	};
Documentation/devicetree/bindings/crypto/ti,omap4-des.yaml new file +66 -0

66 lines not on this page · raw message

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

Convert the TI OMAP DES binding to DT schema format.

Drop "ti,hwmods" as it is not actually used for this binding. Only OMAP2 platforms are using it.

Quoted 8 lines
---
 .../devicetree/bindings/crypto/omap-des.txt   | 30 ---------
 .../bindings/crypto/ti,omap4-des.yaml         | 66 +++++++++++++++++++
 2 files changed, 66 insertions(+), 30 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/crypto/omap-des.txt
 create mode 100644 Documentation/devicetree/bindings/crypto/ti,omap4-des.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-des.example.dtb: des@480a5000 (ti,omap4-des): 'ti,hwmods' is a required property
from schema $id: http://devicetree.org/schemas/ti,omap4-des.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.