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

From: Rob Herring

Date: Tue Aug 11 2026 - 13:49:49 EST


On Tue, Aug 11, 2026 at 09:18:47AM +0000, Eduard Bostina wrote:
> Convert the Texas Instruments Message Manager binding
> to DT schema.
>
> Signed-off-by: Eduard Bostina <egbostina@xxxxxxxxx>
> ---
> .../bindings/mailbox/ti,message-manager.txt | 50 --------------
> .../bindings/mailbox/ti,message-manager.yaml | 69 +++++++++++++++++++
> 2 files changed, 69 insertions(+), 50 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/mailbox/ti,message-manager.txt
> create mode 100644 Documentation/devicetree/bindings/mailbox/ti,message-manager.yaml

ti,k2g-message-manager.yaml for the filename.

> diff --git a/Documentation/devicetree/bindings/mailbox/ti,message-manager.yaml b/Documentation/devicetree/bindings/mailbox/ti,message-manager.yaml
> new file mode 100644
> index 000000000000..01d62fc5a7c4
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mailbox/ti,message-manager.yaml
> @@ -0,0 +1,69 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mailbox/ti,message-manager.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Texas Instruments Message Manager
> +
> +maintainers:
> + - Eduard Bostina <egbostina@xxxxxxxxx>
> +
> +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:
> + minItems: 2
> + maxItems: 2

Just maxItems is enough.

> +
> + 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:
> + minItems: 2
> + maxItems: 2

Just maxItems is enough.