From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4E51F41B340; Fri, 27 Feb 2026 14:53:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772203989; cv=none; b=sMUpVvlTUDV4sMe6kjfjA5tWGUaKqEnq05NIz5apNxZtHsoHwpPGHjV30PbR/hXgNCmKvFFhjfdb+Y8fvQSHbqyDo06Geudwtk9Nvgptif917WLY1iH3+mJjmuMm+nWU14D5PBIg1X4N86fiWxIhEfjUurI+Rq9R+pAxHzx877M= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772203989; c=relaxed/simple; bh=jX6WmKtuN6T2VpqyIezKKD+/Ad5MsTZIssF/fg+tWn8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type; b=EXuP2l71vAZMMQjSAXD1dty7xjfov4lKndkSwfNCD/ai4fx85RdWxkLqPdrJY+uggN64kLL1zp1126nZHETGPIe7AWUhcXPZsjDzWEIFl9qqKgIJxcGrTMHrdbC5YHbXdwC3kP2SySDhSdo4dYu4znqMSGS1K8KMlg4wvLT8LqU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=VeSyfGtR; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="VeSyfGtR" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 961FCC116C6; Fri, 27 Feb 2026 14:53:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772203988; bh=jX6WmKtuN6T2VpqyIezKKD+/Ad5MsTZIssF/fg+tWn8=; h=From:To:Cc:Subject:Date:From; b=VeSyfGtRm1j7SmiqAAty+SxdjG62YxV/HCIdWW4nOuwDqUnmzdR0N1I8BI+AsDOeA 59KLm0CXu4Qd+g7VaHjOpD6oE3QOtu9+3knRhhrFvsZ/C1SE1V6kcQI8XcHPqvcQDO 4Px6DS4hYTqUiqnLOj891BESEM3hdlNXXzapDoME+y8FFOuRt9fgRwC1BV+jkwOPcJ QNdnKVcPRd4hw0n+8mRkOxu3vWF6UtohsWNA9ugcFQN2LP+FYNkP72ZP+RxLsSytDP AYWj41DNWnOizEI+3jSeBgjG8wCdyHfRhw6SqVj/nJkx61BmFMdv2p/BdFGDk7L781 IBbPojHJbe1ng== From: Conor Dooley To: linux-gpio@vger.kernel.org Cc: conor@kernel.org, Conor Dooley , Thomas Gleixner , Herve Codina , Daire McNamara , Rob Herring , Krzysztof Kozlowski , Paul Walmsley , Palmer Dabbelt , Albert Ou , Alexandre Ghiti , Linus Walleij , Bartosz Golaszewski , linux-riscv@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [RFC v11 0/4] PolarFire SoC GPIO interrupt support Date: Fri, 27 Feb 2026 14:52:26 +0000 Message-ID: <20260227-ajar-wolverine-7ce1ebd79821@spud> X-Mailer: git-send-email 2.51.0 Precedence: bulk X-Mailing-List: linux-gpio@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4301; i=conor.dooley@microchip.com; h=from:subject:message-id; bh=mfPuD7/X4c6UDjnGwLM+ANCIFBHCdBf6P3/wkC/hOA8=; b=owGbwMvMwCVWscWwfUFT0iXG02pJDJkL16/5e3/7XX6jBovpz84ILtj94QY/y2mG171X9SceL dp3O8UuoaOUhUGMi0FWTJEl8XZfi9T6Py47nHvewsxhZQIZwsDFKQATcRRnZLg6T9ZQRfhEwNOj 554tXGTX7p7FpxQik1pwk+PXrNetE/4zMnTWK/63vO9wVWY2X5dt4bUFL48ZnkwwXXNhT6K9bWq hNh8A X-Developer-Key: i=conor.dooley@microchip.com; a=openpgp; fpr=F9ECA03CF54F12CD01F1655722E2C55B37CF380C Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Conor Dooley In 2024 I sent a v7 of adding support for the GPIOs on PolarFire SoC, which relied on an irqchip driver for a mux sitting between the GPIO controllers and the main interrupt controller on the chip: https://lore.kernel.org/all/20240723-flatworm-cornflake-8023212f6584@wendy/ Some feedback I got from Thomas there ended up being a complete black hole for time spent, and I never managed to make the change he wanted, as a house of cards collapsed whenever I tried it. I eventually abandoned my attempt to upstream the GPIO driver with interrupt support and cut it out of the driver to make progress. I've been carrying what Thomas deemed incorrect downstream since. Recently Hervé upstreamed a patchset for a Renesas chip that deals with a mux sitting between a GPIO controller and the platform interrupt controller by way of interrupt-map. I saw the opportunity to copy what he did, so have gone from an irqchip driver that read the mux setting that firmware had configured, to trivial driver that reads the mux configuration from devicetree and sets the hardware up to match. This gets rid entirely of the irqchip driver, so resolves Thomas' complaint, but I don't love how the GPIO side of things turned out quite as much. The hardware has 41 interrupts but 70 GPIO lines. 38 of these are 1:1, direct connections to a dedicated line on the interrupt controller and 3 are shared. With the parent mux driver, the GPIO driver's interrupt handler was only called either for specific direct interrupt or for only the subset that are fed into the shared interrupt for that controller. Without the parent irqchip from mux driver, and using interrupt-map, I lost the ability to use mux driver to selectively call the handler, so now the GPIO controller attempts to handle interrupts on all lines. Probably this is ultimately not a big deal, it just feels bad to do. Going RFC here, since it's an entirely different approach. The version number is a continuation from before, since the patchset linked above got merged at v10 when I stripped the interrupt support. The mux driver has moved from irqchip to soc, since that's where Hervé's ended up. Cheers, Conor. CC: Thomas Gleixner CC: Herve Codina CC: Conor Dooley CC: Daire McNamara CC: Rob Herring CC: Krzysztof Kozlowski CC: Paul Walmsley CC: Palmer Dabbelt CC: Albert Ou CC: Alexandre Ghiti CC: Linus Walleij CC: Bartosz Golaszewski CC: linux-riscv@lists.infradead.org CC: devicetree@vger.kernel.org CC: linux-kernel@vger.kernel.org CC: linux-gpio@vger.kernel.org Conor Dooley (4): gpio: mpfs: Add interrupt support dt-bindings: soc: microchip: document PolarFire SoC's gpio interrupt mux soc: microchip: add mpfs gpio interrupt mux driver riscv: dts: microchip: update mpfs gpio interrupts to better match the SoC .../soc/microchip/microchip,mpfs-irqmux.yaml | 76 ++++++++ .../microchip,mpfs-mss-top-sysreg.yaml | 4 + MAINTAINERS | 2 +- .../boot/dts/microchip/mpfs-beaglev-fire.dts | 29 +++ .../boot/dts/microchip/mpfs-disco-kit.dts | 43 +++-- .../dts/microchip/mpfs-icicle-kit-common.dtsi | 37 +++- .../boot/dts/microchip/mpfs-m100pfsevp.dts | 41 +++-- .../boot/dts/microchip/mpfs-polarberry.dts | 29 +++ .../riscv/boot/dts/microchip/mpfs-sev-kit.dts | 37 +++- .../riscv/boot/dts/microchip/mpfs-tysom-m.dts | 35 +++- arch/riscv/boot/dts/microchip/mpfs.dtsi | 37 +++- drivers/gpio/Kconfig | 1 + drivers/gpio/gpio-mpfs.c | 125 ++++++++++++- drivers/soc/microchip/Kconfig | 11 ++ drivers/soc/microchip/Makefile | 1 + drivers/soc/microchip/mpfs-irqmux.c | 167 ++++++++++++++++++ 16 files changed, 620 insertions(+), 55 deletions(-) create mode 100644 Documentation/devicetree/bindings/soc/microchip/microchip,mpfs-irqmux.yaml create mode 100644 drivers/soc/microchip/mpfs-irqmux.c -- 2.51.0