From: Rob Herring <robh@kernel.org>
To: Eduard Bostina <egbostina@gmail.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, Jassi Brar <jassisinghbrar@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, daniel.baluta@nxp.com,
simona.toaca@nxp.com, goledhruva@gmail.com, m-chawdhry@ti.com
Subject: Re: [PATCH] dt-bindings: mailbox: Convert TI Message Manager to DT schema
Date: Tue, 11 Aug 2026 12:49:35 -0500 [thread overview]
Message-ID: <20260811174935.GA2720095-robh@kernel.org> (raw)
In-Reply-To: <20260811091847.686229-1-egbostina@gmail.com>
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@gmail.com>
> ---
> .../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@gmail.com>
> +
> +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.
prev parent reply other threads:[~2026-08-11 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 9:18 [PATCH] dt-bindings: mailbox: Convert TI Message Manager to DT schema Eduard Bostina
2026-08-11 17:49 ` Rob Herring [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260811174935.GA2720095-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=egbostina@gmail.com \
--cc=goledhruva@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=simona.toaca@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox