Thread (6 messages) 6 messages, 5 authors, 2026-03-24

Re: [PATCH] arm64: dts: imx8mp-debix-model-a: Correct PAD settings for pmicirqgrp

From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Date: 2026-03-24 19:43:56
Also in: imx, linux-devicetree, lkml

On Tue, Mar 24, 2026 at 05:38:14PM +0000, Kieran Bingham wrote:
Quoting Laurent Pinchart (2026-03-24 09:38:50)
quoted
On Tue, Mar 24, 2026 at 11:16:13AM +0800, Peng Fan (OSS) wrote:
quoted
From: Peng Fan <peng.fan@nxp.com>

With commit 5d0efaf47ee90 ("regulator: pca9450: Correct interrupt type"),
there is interrupt storm for i.MX8MP DEBIX Model A. Per schematic, there
is no on board PULL-UP resistors for GPIO1_IO03, so need to set PAD
PUE and PU together to make pull up work properly.

Fixes: c86d350aae68e ("arm64: dts: Add device tree for the Debix Model A Board")
Reported-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Closes: https://lore.kernel.org/all/20260323105858.GA2185714@killaraus.ideasonboard.com/ (local)
Signed-off-by: Peng Fan <peng.fan@nxp.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Tested-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

Frank, would you be able to handle this as a v7.0 regression fix ?

I think the same is needed for imx8mp-debix-som-a.dtsi, but I can't
confirm it as I don't have the schematics for the SoM, neither do I have
access to the board.

Dan, Kieran, Stefan, could one of you check if you get an interrupt
storm from the PMIC on v7.0 ?
Confirmed:
 35:      83626          0          0          0 gpio-mxc   3 Level     pca9450-irq

 and

200:     270180          0          0          0    GICv3  67 Level     30a20000.i2c
...
200:     400925          0          0          0    GICv3  67 Level     30a20000.i2c
...

increasing rapidly on the debix-som.

I started out on the linux-media branches which were 7.0-rc2 based, and
this didn't happen but cherry-picking in 5d0efaf47ee90 certainly causes
this issue to occur on my board.
Could you confirm that setting MX8MP_IOMUXC_GPIO1_IO03__GPIO1_IO03 to
0x000001c0 fixes the issue ?
quoted
quoted
---
 arch/arm64/boot/dts/freescale/imx8mp-debix-model-a.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/freescale/imx8mp-debix-model-a.dts b/arch/arm64/boot/dts/freescale/imx8mp-debix-model-a.dts
index 9422beee30b29c5a551b08476c80fbff96af3439..df7489587e48ed0c678f11291f6f2b77082ade95 100644
--- a/arch/arm64/boot/dts/freescale/imx8mp-debix-model-a.dts
+++ b/arch/arm64/boot/dts/freescale/imx8mp-debix-model-a.dts
@@ -440,7 +440,7 @@ MX8MP_IOMUXC_SAI5_RXC__I2C6_SDA                                   0x400001c3
 
      pinctrl_pmic: pmicirqgrp {
              fsl,pins = <
-                     MX8MP_IOMUXC_GPIO1_IO03__GPIO1_IO03                             0x41
+                     MX8MP_IOMUXC_GPIO1_IO03__GPIO1_IO03                             0x000001c0
              >;
      };
 
---
base-commit: 09c0f7f1bcdbc3c37a5a760cbec76bf18f278406
change-id: 20260324-imx8mp-dts-fix-512530fe4dcd
-- 
Regards,

Laurent Pinchart
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help