From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.org, Conor Dooley <conor@kernel.org>
Cc: 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, stable@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: microchip: beaglev-fire: remove double definition of gpio interrupts
Date: Tue, 8 Sep 2026 19:20:27 +0100 [thread overview]
Message-ID: <178889161920.3146991.520958835856287447.b4-ty@microchip.com> (raw)
In-Reply-To: <20260904172253.2274751-3-conor@kernel.org>
From: Conor Dooley <conor.dooley@microchip.com>
On Fri, 04 Sep 2026 18:22:55 +0100, Conor Dooley wrote:
> When the irq-mux and its interrupt-map were added to the mpfs
> devicetree, the gpio interrupts became fixed at the SoC level rather
> than dependant on the design - the interrupt-map is now what varies.
> The beaglev-fire should have had its dts copy of the interrupts removed
> but did not. As a result, the mcp3564 driver does not probe, because
> even though it doesn't use the interrupt at present, the SPI core still
> looks it up. This lookup fails because the second copy of the interrupts
> property doesn't resolve to something valid when passed via the
> interrupt-map. Remove the second/incorrect set of interrupts properties.
>
> [...]
Applied to cache-for-next, thanks!
[1/1] riscv: dts: microchip: beaglev-fire: remove double definition of gpio interrupts
(no commit info)
Thanks,
Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-09-08 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 17:22 [PATCH] riscv: dts: microchip: beaglev-fire: remove double definition of gpio interrupts Conor Dooley
2026-09-08 18:20 ` Conor Dooley [this message]
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=178889161920.3146991.520958835856287447.b4-ty@microchip.com \
--to=conor@kernel.org \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=conor.dooley@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 \
--cc=stable@vger.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