From: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
To: Frank Mori Hess <fmh6jj@gmail.com>,
Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: usb: dwc2: screaming interrupt after kexec reboot
Date: Wed, 27 May 2020 06:06:06 +0000 [thread overview]
Message-ID: <dca3b78a-3740-aeb2-5767-76e7f9fd1fb5@synopsys.com> (raw)
In-Reply-To: <CAJz5Opc0zDQxnNp2foPEeL0=hOZ0C9-xy3T4nEO2pRy-rQmpWQ@mail.gmail.com>
Hi Frank,
On 5/26/2020 7:25 AM, Frank Mori Hess wrote:
> Hi,
>
> I get a screaming dwc2 interrupt after rebooting into a new kernel
> with kexec. I fixed it by modifying the dwc2_driver_shutdown function
> in dwc2/platform.c so it does
>
> dwc2_writel(hsotg, 0, GINTMSK);
> dwc2_writel(hsotg, 0, HAINTMSK);
> dwc2_writel(hsotg, 0, DAINTMSK);
>
> rather than calling disable_irq(). Another reason to make this change
> is disable_irq() affects other devices if the irq is shared. I'd
> really rather not submit a formal patch, hopefully the maintainer will
> adopt this suggestion.
>
Could you please test this patch instead of your suggestion. Does it
solve issue in your case?
diff --git a/drivers/usb/dwc2/platform.c b/drivers/usb/dwc2/platform.c
index e571c8ae65ec..ada5b66b948e 100644
--- a/drivers/usb/dwc2/platform.c
+++ b/drivers/usb/dwc2/platform.c
@@ -342,7 +342,7 @@ static void dwc2_driver_shutdown(struct
platform_device *dev)
{
struct dwc2_hsotg *hsotg = platform_get_drvdata(dev);
- disable_irq(hsotg->irq);
+ dwc2_disable_global_interrupts(hsotg);
}
/**
Thanks,
Minas
next prev parent reply other threads:[~2020-05-27 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 3:25 usb: dwc2: screaming interrupt after kexec reboot Frank Mori Hess
2020-05-27 6:06 ` Minas Harutyunyan [this message]
2020-05-28 19:16 ` Frank Mori Hess
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=dca3b78a-3740-aeb2-5767-76e7f9fd1fb5@synopsys.com \
--to=minas.harutyunyan@synopsys.com \
--cc=fmh6jj@gmail.com \
--cc=linux-usb@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.