public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Levinsky <ben.levinsky@amd.com>
To: <andersson@kernel.org>, <mathieu.poirier@linaro.org>
Cc: <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>, <ben.levinsky@amd.com>,
	<tanmay.shah@amd.com>, <michal.simek@amd.com>
Subject: [PATCH 0/2] Add a MicroBlaze remoteproc driver and binding
Date: Tue, 14 Apr 2026 09:15:56 -0700	[thread overview]
Message-ID: <20260414161558.2579920-1-ben.levinsky@amd.com> (raw)

This series adds initial remoteproc support for AMD MicroBlaze soft
processors.

The binding models the MicroBlaze remote processor as a child node whose
reg property describes the executable firmware memory window in the
MicroBlaze-local address space. The parent bus ranges property provides
the standard devicetree address translation to the Linux-visible system
physical address.

The driver uses that translated memory window as the executable
remoteproc carveout and coredump segment, holds the MicroBlaze in reset
through an active-low GPIO until firmware loading completes, and allows
the firmware image to be selected with the optional firmware-name
property. Firmware images without a resource table are also accepted.

This initial series focuses on basic load/start/stop support for a
single executable memory window. It does not add any transport or
mailbox integration.

Ben Levinsky (2):
  dt-bindings: remoteproc: add AMD MicroBlaze binding
  remoteproc: add AMD MicroBlaze driver

 .../bindings/remoteproc/amd,microblaze.yaml   |  67 ++++++
 MAINTAINERS                                   |   7 +
 drivers/remoteproc/Kconfig                    |  15 ++
 drivers/remoteproc/Makefile                   |   1 +
 drivers/remoteproc/amd_microblaze_rproc.c     | 202 ++++++++++++++++++
 5 files changed, 292 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/remoteproc/amd,microblaze.yaml
 create mode 100644 drivers/remoteproc/amd_microblaze_rproc.c

-- 
2.34.1

             reply	other threads:[~2026-04-14 16:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 16:15 Ben Levinsky [this message]
2026-04-14 16:15 ` [PATCH 1/2] dt-bindings: remoteproc: add AMD MicroBlaze binding Ben Levinsky
2026-04-14 17:29   ` Rob Herring (Arm)
2026-04-14 17:53   ` Krzysztof Kozlowski
2026-04-15  6:16     ` Michal Simek
2026-04-15  6:50       ` Krzysztof Kozlowski
2026-04-15  6:55         ` Michal Simek
2026-04-15  7:07           ` Krzysztof Kozlowski
2026-04-15  8:06             ` Michal Simek
2026-04-15  8:24               ` Krzysztof Kozlowski
2026-04-15  8:35                 ` Michal Simek
2026-04-15 12:19       ` Rob Herring
2026-04-15 12:41         ` Michal Simek
2026-04-14 16:15 ` [PATCH 2/2] remoteproc: add AMD MicroBlaze driver Ben Levinsky
2026-04-14 17:56   ` Krzysztof Kozlowski

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=20260414161558.2579920-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox