Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Levinsky <ben.levinsky@amd.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Jassi Brar <jassisinghbrar@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: <michal.simek@amd.com>, <tanmay.shah@amd.com>,
	<ben.levinsky@amd.com>, <linux-remoteproc@vger.kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/4] Add AMD PL Mailbox and RPMsg support for the AMD BRAM remoteproc
Date: Thu, 19 Nov 2026 14:04:01 -0800	[thread overview]
Message-ID: <20261119220405.2838553-1-ben.levinsky@amd.com> (raw)

This series adds a driver for the AMD PL Mailbox soft IP and uses it to
add RPMsg support to the AMD MicroBlaze/V BRAM remoteproc driver.

Patches 1-2 add the PL Mailbox binding and driver, and patches 3-4 add
RPMsg resources to the BRAM remoteproc binding and driver.

Claude (claude-opus-5.5) was used to help write the code and changelogs,
as indicated by the Assisted-by tags.

Tested on a VEK385 board with the series applied to a 6.18 based AMD
vendor kernel: RPMsg echo with bursts of 64 messages, over five remote
processor start/stop cycles, with two MicroBlaze V designs.

Changes in v3:
- Drop "remoteproc: amd_mbv_bram: Bound device name formatting".  The
  name is already bounded by rproc_mem_entry_init() and a DT node name
  can't contain '%', so there was nothing to fix.
- Drop "remoteproc: amd_mbv_bram: Restore reset GPIO direction after PL
  reconfig".  The problem only shows when the PL is reprogrammed while
  the devices it contains are still bound, which isn't a supported flow.
- dt-bindings: mailbox: Reword the description, which no longer refers
  to a "register aperture" or "processor-facing interfaces".
- remoteproc: amd_mbv_bram: Add RPMsg support:
  - Reject memory regions above 4 GiB, since the remote uses the
    physical address as device address.
  - Validate all memory regions before registering any carveout.

v2: https://lore.kernel.org/r/20261105051902.1646651-1-ben.levinsky@amd.com
v1: https://lore.kernel.org/r/20261014213426.2957480-1-ben.levinsky@amd.com

Ben Levinsky (4):
  dt-bindings: mailbox: Add AMD PL Mailbox IP
  mailbox: Add AMD PL Mailbox soft IP controller
  dt-bindings: remoteproc: Add RPMsg resources to AMD BRAM rproc
  remoteproc: amd_mbv_bram: Add RPMsg support

 .../bindings/mailbox/amd,pl-mailbox-2.1.yaml  |  71 ++++
 .../bindings/remoteproc/amd,bram-rproc.yaml   |  21 +
 MAINTAINERS                                   |   7 +
 drivers/mailbox/Kconfig                       |  11 +
 drivers/mailbox/Makefile                      |   1 +
 drivers/mailbox/amd-pl-mailbox.c              | 378 ++++++++++++++++++
 drivers/remoteproc/Kconfig                    |   5 +
 drivers/remoteproc/amd_mbv_bram_rproc.c       | 295 +++++++++++++-
 8 files changed, 788 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/devicetree/bindings/mailbox/amd,pl-mailbox-2.1.yaml
 create mode 100644 drivers/mailbox/amd-pl-mailbox.c


base-commit: f1715c0c04606ebbe832cc760abf49dfd6f2ae1f
-- 
2.34.1



             reply	other threads:[~2026-11-19 22:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19 22:04 Ben Levinsky [this message]
2026-11-19 22:04 ` [PATCH v3 1/4] dt-bindings: mailbox: Add AMD PL Mailbox IP Ben Levinsky
2026-11-19 22:04 ` [PATCH v3 2/4] mailbox: Add AMD PL Mailbox soft IP controller Ben Levinsky
2026-11-19 22:04 ` [PATCH v3 3/4] dt-bindings: remoteproc: Add RPMsg resources to AMD BRAM rproc Ben Levinsky
2026-11-19 22:04 ` [PATCH v3 4/4] remoteproc: amd_mbv_bram: Add RPMsg support 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=20261119220405.2838553-1-ben.levinsky@amd.com \
    --to=ben.levinsky@amd.com \
    --cc=andersson@kernel.org \
    --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