[PATCH v2] dt-bindings: mailbox: Convert TI Message Manager to DT schema

Convert the Texas Instruments Message Manager binding
to DT schema.

Signed-off-by: Eduard Bostina <[email protected]>
---
Changes in v2:
- Renamed the file to ti,k2g-message-manager.yaml to match the
  compatible.
- Dropped the 'minItems' from 'reg' and 'interrupts'.

Link to v1: https://lore.kernel.org/all/[email protected]/

 .../mailbox/ti,k2g-message-manager.yaml       | 67 +++++++++++++++++++
 .../bindings/mailbox/ti,message-manager.txt   | 50 --------------
 2 files changed, 67 insertions(+), 50 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/mailbox/ti,k2g-message-manager.yaml
 delete mode 100644 Documentation/devicetree/bindings/mailbox/ti,message-manager.txt

diff --git a/Documentation/devicetree/bindings/mailbox/ti,k2g-message-manager.yaml b/Documentation/devicetree/bindings/mailbox/ti,k2g-message-manager.yaml
new file mode 100644
index 000000000000..481b7c8c0e96
--- /dev/null
+++ b/Documentation/devicetree/bindings/mailbox/ti,k2g-message-manager.yaml
@@ -0,0 +1,67 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/mailbox/ti,k2g-message-manager.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Texas Instruments Message Manager
+
+maintainers:
+  - Eduard Bostina <[email protected]>
+
+description:
+  The Texas Instruments Message Manager is a mailbox controller that has
+  configurable queues selectable at SoC (System on Chip) integration. The
+  Message manager is broken up into queues in different address regions
+  that are called "proxies" - each instance is unidirectional and is
+  instantiated at SoC integration level to indicate receive or transmit path.
+
+properties:
+  compatible:
+    const: ti,k2g-message-manager
+
+  reg:
+    maxItems: 2
+
+  reg-names:
+    items:
+      - const: queue_proxy_region
+      - const: queue_state_debug_region
+
+  "#mbox-cells":
+    const: 2
+    description:
+      Contains the queue ID and proxy ID in that order referring to the
+      transfer path.
+
+  interrupts:
+    maxItems: 2
+
+  interrupt-names:
+    items:
+      - const: rx_005
+      - const: rx_057
+
+required:
+  - compatible
+  - reg
+  - reg-names
+  - "#mbox-cells"
+  - interrupts
+  - interrupt-names
+
+additionalProperties: false
+
+examples:
+  - |
+    #include <dt-bindings/interrupt-controller/arm-gic.h>
+
+    msgmgr@2a00000 {
+        compatible = "ti,k2g-message-manager";
+        #mbox-cells = <2>;
+        reg-names = "queue_proxy_region", "queue_state_debug_region";
+        reg = <0x02a00000 0x400000>, <0x028c3400 0x400>;
+        interrupt-names = "rx_005", "rx_057";
+        interrupts = <GIC_SPI 324 IRQ_TYPE_LEVEL_HIGH>,
+                     <GIC_SPI 327 IRQ_TYPE_LEVEL_HIGH>;
+    };
diff --git a/Documentation/devicetree/bindings/mailbox/ti,message-manager.txt b/Documentation/devicetree/bindings/mailbox/ti,message-manager.txt
deleted file mode 100644
index ebf0e3710cee..000000000000
--- a/Documentation/devicetree/bindings/mailbox/ti,message-manager.txt
+++ /dev/null
@@ -1,50 +0,0 @@
-Texas Instruments' Message Manager Driver
-========================================
-
-The Texas Instruments' Message Manager is a mailbox controller that has
-configurable queues selectable at SoC(System on Chip) integration. The Message
-manager is broken up into queues in different address regions that are called
-"proxies" - each instance is unidirectional and is instantiated at SoC
-integration level to indicate receive or transmit path.
-
-Message Manager Device Node:
-===========================
-Required properties:
---------------------
-- compatible:		Shall be: "ti,k2g-message-manager"
-- reg-names 		queue_proxy_region - Map the queue proxy region.
-			queue_state_debug_region - Map the queue state debug
-			region.
-- reg:			Contains the register map per reg-names.
-- #mbox-cells		Shall be 2. Contains the queue ID and proxy ID in that
-		        order referring to the transfer path.
-- interrupt-names:	Contains interrupt names matching the rx transfer path
-			for a given SoC. Receive interrupts shall be of the
-			format: "rx_<QID>".
-			For ti,k2g-message-manager, this shall contain:
-				"rx_005", "rx_057"
-- interrupts:		Contains the interrupt information corresponding to
-			interrupt-names property.
-
-Example(K2G):
-------------
-
-	msgmgr: msgmgr@2a00000 {
-		compatible = "ti,k2g-message-manager";
-		#mbox-cells = <2>;
-		reg-names = "queue_proxy_region", "queue_state_debug_region";
-		reg = <0x02a00000 0x400000>, <0x028c3400 0x400>;
-		interrupt-names = "rx_005", "rx_057";
-		interrupts = <GIC_SPI 324 IRQ_TYPE_LEVEL_HIGH>,
-			     <GIC_SPI 327 IRQ_TYPE_LEVEL_HIGH>;
-	};
-
-	pmmc: pmmc {
-		[...]
-		mbox-names = "rx", "tx";
-		# RX queue ID is 5, proxy ID is 2
-		# TX queue ID is 0, proxy ID is 0
-		mboxes= <&msgmgr 5 2>,
-			<&msgmgr 0 0>;
-		[...]
-	};
-- 
2.43.0