Skip to contentSkip to conversation

dt-bindings: fsl: convert m4if.txt and tigerp.txt to yaml format

PATCH Applied Frank Li 2 participants 2 messages Apr 17, 2025 – Apr 22, 2025

Subsystems (2)
lore
Share & tools
lore

Frank Li

author maintainer
#0 lore raw

PATCH 1/1 dt-bindings: fsl: convert m4if.txt and tigerp.txt to yaml format

Convert m4if.txt and tigerp.txt to yaml format. These just use reg to indicate memory region.

Additional changes:
- Add compatible string fsl,imx51-aipstz.
- Add fsl,imx53-tigerp and fail back to fsl,imx51-tigerp
- Add compatible string fsl,imx7d-pcie-phy, which is not real phy and just indicate a memory region.

---
 .../arm/freescale/fsl,imx51-m4if.yaml         | 41 +++++++++++++++++++
 .../bindings/arm/freescale/m4if.txt           | 12 ------
 .../bindings/arm/freescale/tigerp.txt         | 12 ------
 3 files changed, 41 insertions(+), 24 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,imx51-m4if.yaml
 delete mode 100644 Documentation/devicetree/bindings/arm/freescale/m4if.txt
 delete mode 100644 Documentation/devicetree/bindings/arm/freescale/tigerp.txt
Documentation/devicetree/bindings/arm/freescale/fsl,imx51-m4if.yaml new file +41 -0
new file mode 100644
index 0000000000000..1f515bea39599
@@ -0,0 +1,41 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/arm/freescale/fsl,imx51-m4if.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Freescale Multi Master Multi Memory Interface (M4IF) and Tigerp module
+
+description: collect the imx devices, which only have compatible and reg property
+
+maintainers:
+  - Frank Li <[email protected]>
+
+properties:
+  compatible:
+    oneOf:
+      - enum:
+          - fsl,imx51-m4if
+          - fsl,imx51-tigerp
+          - fsl,imx51-aipstz
+          - fsl,imx53-aipstz
+          - fsl,imx7d-pcie-phy
+      - items:
+          - const: fsl,imx53-tigerp
+          - const: fsl,imx51-tigerp
+
+  reg:
+    maxItems: 1
+
+required:
+  - compatible
+  - reg
+
+additionalProperties: false
+
+examples:
+  - |
+    m4if@83fd8000 {
+        compatible = "fsl,imx51-m4if";
+        reg = <0x83fd8000 0x1000>;
+    };
Documentation/devicetree/bindings/arm/freescale/m4if.txt deleted +0 -12
deleted file mode 100644
index 93bd7b867a536..0000000000000
@@ -1,12 +0,0 @@
-* Freescale Multi Master Multi Memory Interface (M4IF) module
-
-Required properties:
-- compatible : Should be "fsl,imx51-m4if"
-- reg : Address and length of the register set for the device
-
-Example:
-
-m4if: m4if@83fd8000 {
-	compatible = "fsl,imx51-m4if";
-	reg = <0x83fd8000 0x1000>;
-};
Documentation/devicetree/bindings/arm/freescale/tigerp.txt deleted +0 -12
deleted file mode 100644
index 19e2aad63d6ef..0000000000000
@@ -1,12 +0,0 @@
-* Freescale Tigerp platform module
-
-Required properties:
-- compatible : Should be "fsl,imx51-tigerp"
-- reg : Address and length of the register set for the device
-
-Example:
-
-tigerp: tigerp@83fa0000 {
-	compatible = "fsl,imx51-tigerp";
-	reg = <0x83fa0000 0x28>;
-};
Signature · 1 line
2.34.1
maintainer Applied
#1 lore raw
Quoted 10 lines · Frank Li

Convert m4if.txt and tigerp.txt to yaml format. These just use reg to indicate memory region.

Additional changes:
- Add compatible string fsl,imx51-aipstz.
- Add fsl,imx53-tigerp and fail back to fsl,imx51-tigerp
- Add compatible string fsl,imx7d-pcie-phy, which is not real phy and just indicate a memory region.

Quoted 9 lines
---
 .../arm/freescale/fsl,imx51-m4if.yaml         | 41 +++++++++++++++++++
 .../bindings/arm/freescale/m4if.txt           | 12 ------
 .../bindings/arm/freescale/tigerp.txt         | 12 ------
 3 files changed, 41 insertions(+), 24 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,imx51-m4if.yaml
 delete mode 100644 Documentation/devicetree/bindings/arm/freescale/m4if.txt
 delete mode 100644 Documentation/devicetree/bindings/arm/freescale/tigerp.txt

Applied, thanks!