From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.org
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Valentina.FernandezAlanis@microchip.com,
Brian.Burke@microchip.com, cyril.jean@microchip.com
Subject: [PATCH v1 1/5] riscv: dts: microchip: gpio controllers on mpfs need 2 interrupt cells
Date: Thu, 19 Mar 2026 16:31:15 +0000 [thread overview]
Message-ID: <20260319-crushable-outhouse-e06ca969a01d@spud> (raw)
In-Reply-To: <20260319-outsell-hypnotic-94b480408ad4@spud>
From: Conor Dooley <conor.dooley@microchip.com>
The platform has variable interrupt types for GPIO interrupts, in
addition to having multiple lines per GPIO controller. Two interrupt
cells are required.
Fixes: 528a5b1f2556d ("riscv: dts: microchip: add new peripherals to icicle kit device tree")
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
arch/riscv/boot/dts/microchip/mpfs.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/riscv/boot/dts/microchip/mpfs.dtsi b/arch/riscv/boot/dts/microchip/mpfs.dtsi
index 5c2963e269b83..8cca84484b85d 100644
--- a/arch/riscv/boot/dts/microchip/mpfs.dtsi
+++ b/arch/riscv/boot/dts/microchip/mpfs.dtsi
@@ -473,7 +473,7 @@ gpio0: gpio@20120000 {
reg = <0x0 0x20120000 0x0 0x1000>;
interrupt-parent = <&plic>;
interrupt-controller;
- #interrupt-cells = <1>;
+ #interrupt-cells = <2>;
clocks = <&clkcfg CLK_GPIO0>;
gpio-controller;
#gpio-cells = <2>;
@@ -485,7 +485,7 @@ gpio1: gpio@20121000 {
reg = <0x0 0x20121000 0x0 0x1000>;
interrupt-parent = <&plic>;
interrupt-controller;
- #interrupt-cells = <1>;
+ #interrupt-cells = <2>;
clocks = <&clkcfg CLK_GPIO1>;
gpio-controller;
#gpio-cells = <2>;
@@ -497,7 +497,7 @@ gpio2: gpio@20122000 {
reg = <0x0 0x20122000 0x0 0x1000>;
interrupt-parent = <&plic>;
interrupt-controller;
- #interrupt-cells = <1>;
+ #interrupt-cells = <2>;
clocks = <&clkcfg CLK_GPIO2>;
gpio-controller;
#gpio-cells = <2>;
--
2.51.0
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-03-19 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 16:31 [PATCH v1 0/5] riscv: dts: minor beaglev-fire improvements Conor Dooley
2026-03-19 16:31 ` Conor Dooley [this message]
2026-03-19 16:31 ` [PATCH v1 2/5] riscv: dts: microchip: remove gpio hogs from beaglev-fire Conor Dooley
2026-03-19 16:31 ` [PATCH v1 3/5] riscv: dts: microchip: clean up beaglev-fire regulator node names Conor Dooley
2026-03-19 16:31 ` [PATCH v1 4/5] riscv: dts: microchip: add adc interrupt on beaglev-fire Conor Dooley
2026-03-19 16:31 ` [PATCH v1 5/5] riscv: dts: microchip: add gpio line names " Conor Dooley
2026-05-05 9:47 ` [PATCH v1 0/5] riscv: dts: minor beaglev-fire improvements Conor Dooley
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=20260319-crushable-outhouse-e06ca969a01d@spud \
--to=conor@kernel.org \
--cc=Brian.Burke@microchip.com \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=conor.dooley@microchip.com \
--cc=cyril.jean@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--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