GPIO34 IRQ is not fired

(Using Jetpack 5.1.2)

I wrote a driver that uses a GPIO as interrupt source (GPIO34) on the AGX Xavier.
The interrupt is mapped in the drivers probe using a regmap and regmap_add_irq_chip using the pin and IRQF_TRIGGER_HIGH as a trigger.

For a while firing the interrutps goes well, after a higher amount of interrupts, the Xavier does not read the interrupt anymore.
I checked the level of the pin and it is high so the function should be called.

I added debug prints in the regmap-irq.c, regmap_irq_thread.
In working conditions, this debug is printed.
There is no other software or driver claiming the same interrupt pin.

I suspect the Xavier of locking something up or ignoring it.
The time between interrupts is very small, that is the reason I use IRQF_TRIGGER_HIGH, just in case a new interrupt is already fired before the first one is handled.

Any help on this?

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.

Hi Ayrton_Leyssens,

Are you using the devkit or custom board for AGX Xavier?

Are you using the following pin as interrupt?

What’s the amount you mean for “higher”?