From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ben Levinsky <ben.levinsky@amd.com>
Cc: jassisinghbrar@gmail.com, andersson@kernel.org,
mathieu.poirier@linaro.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, michal.simek@amd.com,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, tanmay.shah@amd.com
Subject: Re: [PATCH 3/6] dt-bindings: mailbox: Add AMD PL Mailbox IP
Date: Thu, 15 Oct 2026 11:46:42 +0200 [thread overview]
Message-ID: <20261015-humble-eager-mushroom-9db4aa@quoll> (raw)
In-Reply-To: <20261014213426.2957480-4-ben.levinsky@amd.com>
On Wed, Oct 14, 2026 at 02:34:23PM -0700, Ben Levinsky wrote:
> Document the AMD programmable-logic Mailbox IP used for bidirectional
> FIFO communication between two processor-facing interfaces.
>
> The same IP is used on ZynqMP, Versal, Versal NET and Versal Gen 2.
> Name each SoC in its compatible, and use amd,zynqmp-pl-mbox-2.1 as the
> fallback that drivers match.
>
> Define the transmit and receive channel indices together with the register
> aperture, interrupt, and interface clock. Describe the FIFO depth chosen
> when the IP is configured, so that the driver can size received messages
> to it.
>
> Assisted-by: LLM sparse
How sparse assists here? It's something new. Since when does it parse
yaml code?
> Signed-off-by: Ben Levinsky <ben.levinsky@amd.com>
> ---
> .../mailbox/amd,zynqmp-pl-mbox-2.1.yaml | 74 +++++++++++++++++++
> 1 file changed, 74 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mailbox/amd,zynqmp-pl-mbox-2.1.yaml
>
> diff --git a/Documentation/devicetree/bindings/mailbox/amd,zynqmp-pl-mbox-2.1.yaml b/Documentation/devicetree/bindings/mailbox/amd,zynqmp-pl-mbox-2.1.yaml
> new file mode 100644
> index 000000000000..2cc0d106b888
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mailbox/amd,zynqmp-pl-mbox-2.1.yaml
> @@ -0,0 +1,74 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mailbox/amd,zynqmp-pl-mbox-2.1.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: AMD Programmable Logic Mailbox IP
> +
> +maintainers:
> + - Ben Levinsky <ben.levinsky@amd.com>
> +
> +description: |
> + The AMD Programmable Logic Mailbox IP provides bidirectional message passing
> + between two processor-facing interfaces. Each interface writes messages to
> + a send FIFO and reads messages from a receive FIFO. The register aperture,
> + interrupt, and clock described by a node belong to one processor-facing
> + interface. Channel 0 represents transmit and channel 1 represents receive
> + for that interface.
> +
> +properties:
> + compatible:
> + oneOf:
> + - const: amd,zynqmp-pl-mbox-2.1
What is 2.1? Your SoC has different versions?
> + - items:
> + - enum:
> + - amd,versal-pl-mbox-2.1
> + - amd,versal-net-pl-mbox-2.1
> + - amd,versal2-pl-mbox-2.1
> + - const: amd,zynqmp-pl-mbox-2.1
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + amd,mbox-pl-fifo-len:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + minimum: 16
> + maximum: 8192
> + default: 16
> + description:
> + Depth of the send and receive FIFOs in 32-bit words, as configured by
> + the C_MAILBOX_DEPTH parameter of the IP. Must match the configured
> + depth.
So you have multiple mailboxes per one soc different in this?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-15 9:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 21:34 [PATCH 0/6] Add AMD PL Mailbox and RPMsg support for the AMD BRAM remoteproc Ben Levinsky
2026-10-14 21:34 ` [PATCH 1/6] remoteproc: amd_mbv_bram: Bound device name formatting Ben Levinsky
2026-10-14 21:48 ` sashiko-bot
2026-10-14 21:34 ` [PATCH 2/6] remoteproc: amd_mbv_bram: Restore reset GPIO direction after PL reconfig Ben Levinsky
2026-10-14 21:44 ` sashiko-bot
2026-10-14 21:34 ` [PATCH 3/6] dt-bindings: mailbox: Add AMD PL Mailbox IP Ben Levinsky
2026-10-15 9:46 ` Krzysztof Kozlowski [this message]
[not found] ` <DM4PR12MB644859F1CA3A936684A3338B839C2@DM4PR12MB6448.namprd12.prod.outlook.com>
2026-10-15 14:29 ` Ben Levinsky
2026-10-15 15:31 ` Shah, Tanmay
2026-10-14 21:34 ` [PATCH 4/6] mailbox: Add AMD PL Mailbox soft IP controller Ben Levinsky
2026-10-14 21:41 ` sashiko-bot
2026-10-15 9:48 ` Krzysztof Kozlowski
[not found] ` <DM4PR12MB6448B4B18D0B45CCA678814F839C2@DM4PR12MB6448.namprd12.prod.outlook.com>
2026-10-15 14:30 ` Ben Levinsky
2026-10-14 21:34 ` [PATCH 5/6] dt-bindings: remoteproc: Add RPMsg resources to AMD BRAM rproc Ben Levinsky
2026-10-15 9:49 ` Krzysztof Kozlowski
[not found] ` <DM4PR12MB64480F027338BA7A1EF91E17839C2@DM4PR12MB6448.namprd12.prod.outlook.com>
2026-10-15 14:32 ` Ben Levinsky
2026-10-14 21:34 ` [PATCH 6/6] remoteproc: amd_mbv_bram: Add RPMsg support Ben Levinsky
2026-10-14 21:45 ` sashiko-bot
2026-10-15 9:51 ` Krzysztof Kozlowski
[not found] ` <DM4PR12MB6448FDE3208DB753A37EF3F9839C2@DM4PR12MB6448.namprd12.prod.outlook.com>
2026-10-15 14:33 ` Ben Levinsky
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=20261015-humble-eager-mushroom-9db4aa@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=ben.levinsky@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=michal.simek@amd.com \
--cc=robh@kernel.org \
--cc=tanmay.shah@amd.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