From: Ben Levinsky <ben.levinsky@amd.com>
To: <andersson@kernel.org>, <mathieu.poirier@linaro.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <michal.simek@amd.com>, <tanmay.shah@amd.com>, <ben.levinsky@amd.com>
Subject: [PATCH v2 0/2] remoteproc: add AMD BRAM-based remote processor driver
Date: Mon, 27 Apr 2026 09:27:01 -0700 [thread overview]
Message-ID: <20260427162703.1644103-1-ben.levinsky@amd.com> (raw)
Add a BRAM-based remoteproc driver and corresponding binding
for AMD soft processors located in programmable logic.
v2:
This version pivots the series away from a MicroBlaze-specific
binding and driver shape and instead models a BRAM-based soft-core
processor subsystem more generally.
This follows the upstream feedback that amd,microblaze was too tied
to the processor architecture while also being too generic as a DT
compatible for the hardware interface being described.
Patch 1, dt-bindings: remoteproc: document AMD BRAM-based rproc
- Renamed the binding away from amd,microblaze and reframed it
around a BRAM-based soft-core processor subsystem.
- Dropped the redundant trailing "binding" wording from the patch
subject.
- Rewrote the binding text to describe the hardware rather than the
Linux remoteproc framework.
- Reworked the example to address the original dt_binding_check
complaints about the root node and simple-pm-bus example shape.
- Added a clocks property for the soft-core subsystem.
Patch 2, remoteproc: add AMD BRAM-based remote processor driver
- Renamed the driver away from the MicroBlaze-specific name to match
the BRAM-based binding.
- Added clock handling for the soft-core subsystem and the matching
COMMON_CLK dependency in Kconfig.
- Cleaned up the reset comments and removed the success dev_dbg()
message called out in review.
Ben Levinsky (2):
dt-bindings: remoteproc: document AMD BRAM-based rproc
remoteproc: add AMD BRAM-based remote processor driver
.../bindings/remoteproc/amd,bram-rproc.yaml | 98 +++++++
MAINTAINERS | 7 +
drivers/remoteproc/Kconfig | 14 +
drivers/remoteproc/Makefile | 1 +
drivers/remoteproc/amd_bram_rproc.c | 243 ++++++++++++++++++
5 files changed, 363 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/amd,bram-rproc.yaml
create mode 100644 drivers/remoteproc/amd_bram_rproc.c
--
2.34.1
next reply other threads:[~2026-04-27 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 16:27 Ben Levinsky [this message]
2026-04-27 16:27 ` [PATCH v2 1/2] dt-bindings: remoteproc: document AMD BRAM-based rproc Ben Levinsky
2026-04-28 6:50 ` Krzysztof Kozlowski
2026-04-28 8:33 ` Michal Simek
2026-04-28 8:47 ` Krzysztof Kozlowski
2026-04-28 9:04 ` Michal Simek
2026-04-28 9:14 ` Krzysztof Kozlowski
2026-04-28 13:09 ` Michal Simek
2026-04-28 13:12 ` Krzysztof Kozlowski
2026-04-28 13:18 ` Michal Simek
2026-04-28 13:28 ` Krzysztof Kozlowski
2026-04-27 16:27 ` [PATCH v2 2/2] remoteproc: add AMD BRAM-based remote processor driver 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=20260427162703.1644103-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=krzk+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.