From: Francesco Valla <francesco@valla.it>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Fabian Pflug <f.pflug@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Haidong Zheng <haidong.zheng@nxp.com>,
Danwei Luo <danwei.luo@nxp.com>, Lei Xu <lei.xu@nxp.com>
Subject: Re: [PATCH v4 2/2] arm64: dts: freescale: add support for NXP i.MX93 FRDM
Date: Tue, 30 Dec 2025 18:51:07 +0100 [thread overview]
Message-ID: <aVQRCzq8-Q5FguTN@bywater> (raw)
In-Reply-To: <20251230172427.4f22ac7c@windsurf>
Hello Thomas,
On Tue, Dec 30, 2025 at 05:24:27PM +0100, Thomas Petazzoni wrote:
> Hello (again),
>
> On Tue, 30 Dec 2025 17:15:48 +0100
> Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
>
> > I see the PMIC interrupt and the RTC interrupts are routed to the I2C
> > GPIO expander at 1-0022, so I imagine either the PMIC or the RTC are
> > triggering an interrupt (left enabled by U-Boot), and the kernel isn't
> > compiled with the driver for either the PMIC or the RTC, and therefore
> > there's no IRQ handler?
> >
> > (I confess I didn't investigate more than that at this point.)
>
> Upon closer inspection, I in fact get thousands over IRQ #100 per
> seconds right after boot, until the point where it reaches 100000 IRQ
> events, and the splat appears, with the IRQ being subsequently
> disabled. So it's not just one interrupt, but a storm of it.
>
This recalls the behaviour seen on i.MX91 FRDM [0], and the hardware is
indeed very similar: the GPIO expander and the TypeC port controller
(PTN5110) share the same IRQ line, and if the first gets enabled before
the second an interrupt storm will happen (because the PTN5110 is
triggering interrupts that nobody services).
I did not see this during my testing - but maybe the probe sequence is
different. Any chance you are not loading the driver for the PTN5110?
I see from your defconfig it should be compiled as module, but maybe
you are not including it into the image or not loading it?
The NXP downstream BSP is masking interrupts for the TypeC port
controller as part of the U-Boot initialization, as they are enabled by
default at reset. While it somewhat breaks the required isolation
between the bootloader and the system it loads, I fear this is the only
sensible option here, given this hardware limitation; this was the path
that was chosen for the i.MX91 FRDM (which has been applied today [1]).
> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering and training
> https://bootlin.com
>
[0] https://lore.kernel.org/all/aTBFCc-8NzeS4MzT@bywater/
[1] https://lore.kernel.org/u-boot/CAOMZO5DsCi6GHrkvLEZTjsLy1D02A2e83YgMO36b3EMt8B6c5Q@mail.gmail.com/
Reagrds,
Francesco
next prev parent reply other threads:[~2025-12-30 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 11:39 [PATCH v4 0/2] Add devicetree for NXP i.MX93 FRDM board Fabian Pflug
2025-12-18 11:39 ` [PATCH v4 1/2] dt-bindings: arm: fsl: add i.MX93 11x11 " Fabian Pflug
2025-12-18 11:39 ` [PATCH v4 2/2] arm64: dts: freescale: add support for NXP i.MX93 FRDM Fabian Pflug
2025-12-18 21:29 ` Francesco Valla
2025-12-30 16:15 ` Thomas Petazzoni
2025-12-30 16:24 ` Thomas Petazzoni
2025-12-30 17:51 ` Francesco Valla [this message]
2025-12-18 12:52 ` [PATCH v4 0/2] Add devicetree for NXP i.MX93 FRDM board Ahmad Fatoum
2025-12-18 13:11 ` Fabian Pflug
2025-12-18 13:53 ` Ahmad Fatoum
2025-12-30 8:39 ` Shawn Guo
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=aVQRCzq8-Q5FguTN@bywater \
--to=francesco@valla.it \
--cc=conor+dt@kernel.org \
--cc=danwei.luo@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=f.pflug@pengutronix.de \
--cc=festevam@gmail.com \
--cc=haidong.zheng@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lei.xu@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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