From: Thomas Gleixner <tglx@linutronix.de>
To: Stefan Wahren <wahrenst@gmx.net>, Lukas Wunner <lukas@wunner.de>,
Minas Harutyunyan <hminas@synopsys.com>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
bcm-kernel-feedback-list@broadcom.com,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Marc Zyngier <maz@kernel.org>
Subject: Re: dwc2: irq 66: nobody cared triggered on resume
Date: Mon, 24 Jun 2024 20:17:34 +0200 [thread overview]
Message-ID: <87y16u6w8x.ffs@tglx> (raw)
In-Reply-To: <3fd0c2fb-4752-45b3-94eb-42352703e1fd@gmx.net>
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
prev parent reply other threads:[~2024-06-24 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 12:23 dwc2: irq 66: nobody cared triggered on resume Stefan Wahren
[not found] ` <ZnccVLINb_xQcmZG@wunner.de>
2024-06-23 13:27 ` Stefan Wahren
2024-06-24 17:02 ` Stefan Wahren
2024-06-24 18:17 ` Thomas Gleixner [this message]
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=87y16u6w8x.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=hminas@synopsys.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=maz@kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=wahrenst@gmx.net \
/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