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 1/2] dt-bindings: remoteproc: add AMD MicroBlaze binding
Date: Tue, 14 Apr 2026 09:15:57 -0700 [thread overview]
Message-ID: <20260414161558.2579920-2-ben.levinsky@amd.com> (raw)
In-Reply-To: <20260414161558.2579920-1-ben.levinsky@amd.com>
Describe an AMD MicroBlaze remote processor controlled
through the remoteproc framework.
The binding models the MicroBlaze remoteproc device as a
child node whose reg property describes the executable firmware
memory window in the MicroBlaze-local address space. The parent bus
node provides standard devicetree address translation through ranges
so Linux can access the same memory through the system physical
address space.
An active-low reset GPIO holds the MicroBlaze in reset until
firmware loading completes.
Signed-off-by: Ben Levinsky <ben.levinsky@amd.com>
---
.../bindings/remoteproc/amd,microblaze.yaml | 67 +++++++++++++++++++
1 file changed, 67 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/amd,microblaze.yaml
diff --git a/Documentation/devicetree/bindings/remoteproc/amd,microblaze.yaml b/Documentation/devicetree/bindings/remoteproc/amd,microblaze.yaml
new file mode 100644
index 000000000000..2811610204a9
--- /dev/null
+++ b/Documentation/devicetree/bindings/remoteproc/amd,microblaze.yaml
@@ -0,0 +1,67 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/remoteproc/amd,microblaze.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: AMD MicroBlaze remote processor
+
+maintainers:
+ - Ben Levinsky <ben.levinsky@amd.com>
+
+description:
+ MicroBlaze remote processor controlled by Linux through the remoteproc
+ framework.
+
+ The executable firmware memory window is described in the
+ MicroBlaze-local address space by the node's reg property and translated
+ to the system physical address space with standard devicetree address
+ translation provided by the parent bus node's ranges property.
+
+properties:
+ $nodename:
+ pattern: "^remoteproc@[0-9a-f]+$"
+
+ compatible:
+ const: amd,microblaze
+
+ reg:
+ maxItems: 1
+ description:
+ MicroBlaze-local address and size of the executable firmware memory
+ window.
+
+ firmware-name:
+ maxItems: 1
+
+ reset-gpios:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+ - reset-gpios
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+
+ / {
+ #address-cells = <2>;
+ #size-cells = <2>;
+
+ bus@b0000000 {
+ compatible = "simple-pm-bus";
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges = <0x0 0x0 0xb0000000 0x40000>;
+
+ remoteproc@0 {
+ compatible = "amd,microblaze";
+ reg = <0x0 0x40000>;
+ reset-gpios = <&mbv_reset_gpio 0 GPIO_ACTIVE_LOW>;
+ };
+ };
+ };
--
2.34.1
next prev parent 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 [PATCH 0/2] Add a MicroBlaze remoteproc driver and binding Ben Levinsky
2026-04-14 16:15 ` Ben Levinsky [this message]
2026-04-14 17:29 ` [PATCH 1/2] dt-bindings: remoteproc: add AMD MicroBlaze binding 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-2-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