From: tze.yee.ng@altera.com
To: Dinh Nguyen <dinguyen@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mahesh Rao <mahesh.rao@altera.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: Tze Yee Ng <tze.yee.ng@altera.com>,
Adrian Ng Ho Yin <adrian.ho.yin.ng@altera.com>,
Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
Subject: [PATCH 0/2] dt-bindings: arm64: dts: Intel SoCFPGA: rsu-handle on svc for U-Boot
Date: Wed, 6 May 2026 05:42:19 -0700 [thread overview]
Message-ID: <cover.1778070377.git.tze.yee.ng@altera.com> (raw)
From: Tze Yee Ng <tze.yee.ng@altera.com>
When Linux passes a device tree to U-Boot for remote system update (RSU),
U-Boot needs to know which QSPI partition holds the boot image. Add an
optional rsu-handle property on the Intel service-layer (svc) node: it is
a phandle to the board's QSPI boot partition (typically labeled
qspi_boot).
Patch 1 documents rsu-handle in the intel,stratix10-svc binding (shared by
Stratix 10, Agilex, and Agilex5 svc compatibles) and extends the example
so the qspi_boot label and reg cells are valid for dt_binding_check.
Patch 2 labels the firmware svc node as "svc" in the Stratix 10, Agilex,
and Agilex5 SoC .dtsi files, and sets rsu-handle = <&qspi_boot> via &svc
only on board .dts files that already define qspi_boot. Boards without
that partition are unchanged and avoid an unresolved phandle.
Tze Yee Ng (2):
dt-bindings: firmware: document rsu-handle for intel stratix10-svc
arm64: dts: socfpga: add rsu-handle to svc on QSPI SoCDK boards
.../firmware/intel,stratix10-svc.yaml | 25 +++++++++++++++++++
.../boot/dts/altera/socfpga_stratix10.dtsi | 2 +-
.../dts/altera/socfpga_stratix10_socdk.dts | 4 +++
.../altera/socfpga_stratix10_socdk_nand.dts | 4 +++
arch/arm64/boot/dts/intel/socfpga_agilex.dtsi | 2 +-
.../boot/dts/intel/socfpga_agilex3_socdk.dts | 4 +++
.../arm64/boot/dts/intel/socfpga_agilex5.dtsi | 2 +-
.../boot/dts/intel/socfpga_agilex5_socdk.dts | 4 +++
.../dts/intel/socfpga_agilex5_socdk_013b.dts | 4 +++
.../intel/socfpga_agilex5_socdk_modular.dts | 4 +++
.../boot/dts/intel/socfpga_agilex_socdk.dts | 4 +++
.../boot/dts/intel/socfpga_n5x_socdk.dts | 4 +++
12 files changed, 60 insertions(+), 3 deletions(-)
--
2.43.7
next reply other threads:[~2026-05-06 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 12:42 tze.yee.ng [this message]
2026-05-06 12:42 ` [PATCH 1/2] dt-bindings: firmware: document rsu-handle for intel stratix10-svc tze.yee.ng
2026-05-06 13:12 ` Krzysztof Kozlowski
2026-05-06 13:22 ` Rob Herring (Arm)
2026-05-06 12:42 ` [PATCH 2/2] arm64: dts: socfpga: add rsu-handle to svc on QSPI SoCDK boards tze.yee.ng
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=cover.1778070377.git.tze.yee.ng@altera.com \
--to=tze.yee.ng@altera.com \
--cc=adrian.ho.yin.ng@altera.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh.rao@altera.com \
--cc=muhammad.nazim.amirul.nazle.asmade@altera.com \
--cc=robh@kernel.org \
/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.