From: "Alexandra Østermark via B4 Relay" <devnull+alex.cramt.gmail.com@kernel.org>
To: Dinh Nguyen <dinguyen@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Mahesh Rao" <mahesh.rao@altera.com>,
"Mohamad Asyraaf Azhar" <mohamad.asyraaf.azhar@altera.com>,
"Alexandra Østermark" <alex.cramt@gmail.com>
Subject: [PATCH 1/3] arm64: dts: socfpga: agilex5: add the service layer interrupt
Date: Wed, 18 Nov 2026 20:07:13 +0100 [thread overview]
Message-ID: <20261118-de25-nano-v1-1-473d16131f7a@gmail.com> (raw)
In-Reply-To: <20261118-de25-nano-v1-0-473d16131f7a@gmail.com>
From: Alexandra Østermark <alex.cramt@gmail.com>
The SDM signals completion of asynchronous service layer requests on
GIC SPI 0, which the Stratix 10 and Agilex 7 device trees already wire
up, as does Altera's vendor tree for Agilex 5. Upstream's Agilex 5 svc
node lacks it, so stratix10-svc logs "Failed to get IRQ, falling back
to polling mode" and polls for every async reply.
Add the interrupt as the other SoCs do. Tested on a Terasic DE25-Nano:
the driver registers it for sip async operations, it fires
(/proc/interrupts counts it), and FPGA configuration through the FPGA
manager still works.
Signed-off-by: Alexandra Østermark <alex.cramt@gmail.com>
---
arch/arm64/boot/dts/altera/socfpga_agilex5.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/altera/socfpga_agilex5.dtsi b/arch/arm64/boot/dts/altera/socfpga_agilex5.dtsi
index 161f3d4bb..d272cc4fd 100644
--- a/arch/arm64/boot/dts/altera/socfpga_agilex5.dtsi
+++ b/arch/arm64/boot/dts/altera/socfpga_agilex5.dtsi
@@ -84,6 +84,8 @@ svc {
compatible = "intel,agilex5-svc";
method = "smc";
memory-region = <&service_reserved>;
+ interrupts = <GIC_SPI 0 IRQ_TYPE_LEVEL_HIGH>;
+ interrupt-parent = <&intc>;
iommus = <&smmu 10>;
fpga_mgr: fpga-mgr {
--
2.56.0
next prev parent reply other threads:[~2026-11-18 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 19:07 [PATCH 0/3] arm64: dts: socfpga: agilex5: add support for Terasic DE25-Nano Alexandra Østermark via B4 Relay
2026-11-18 19:07 ` Alexandra Østermark via B4 Relay [this message]
2026-11-18 19:07 ` [PATCH 2/3] dt-bindings: arm: altera: add " Alexandra Østermark via B4 Relay
2026-11-18 19:07 ` [PATCH 3/3] arm64: dts: socfpga: agilex5: add support for " Alexandra Østermark via B4 Relay
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=20261118-de25-nano-v1-1-473d16131f7a@gmail.com \
--to=devnull+alex.cramt.gmail.com@kernel.org \
--cc=alex.cramt@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh.rao@altera.com \
--cc=mohamad.asyraaf.azhar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®