dwc2: irq 66: nobody cared triggered on resume
Thomas Gleixner
tglx at linutronix.de
Mon Jun 24 11:17:34 PDT 2024
On Mon, Jun 24 2024 at 19:02, Stefan Wahren wrote:
>
> Is disabling the IRQ via the upper layers an expected behavior instead
> of letting the DWC2 controller driver resolve the situation?
It can't because it's an interrupt storm, i.e. 100k unhandled interrupts
in a row. So the system would just stay there forever.
So one way to solve this is to disable the interrupt accross suspend
resume and only reenable it once everything is in functional state
again.
Thanks,
tglx
More information about the linux-arm-kernel
mailing list