From: Alan Stern <stern@rowland.harvard.edu>
To: Yinbo Zhu <zhuyinbo@loongson.cn>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <greg@kroah.com>,
Patchwork Bot <patchwork-bot@kernel.org>
Subject: Re: [PATCH v6] usb: ohci: disable start-of-frame interrupt in ohci_rh_suspend
Date: Wed, 13 Oct 2021 10:06:22 -0400 [thread overview]
Message-ID: <20211013140622.GA893308@rowland.harvard.edu> (raw)
In-Reply-To: <1634095928-29639-1-git-send-email-zhuyinbo@loongson.cn>
On Wed, Oct 13, 2021 at 11:32:08AM +0800, Yinbo Zhu wrote:
> While going into S3 or S4 suspend, an OHCI host controller can
> generate interrupt requests if the INTR_SF enable flag is set. The
> interrupt handler routine isn't prepared for this and it doesn't turn
> off the flag, causing an interrupt storm.
>
> To fix this problem, make ohci_rh_suspend() always disable INTR_SF
> interrupts after processing the done list and the ED unlinks but
> before the controller goes into the suspended (non-UsbOperational)
> state. There's no reason to leave the flag enabled, since a
> suspended controller doesn't generate Start-of-Frame packets.
>
> Signed-off-by: Yinbo Zhu <zhuyinbo@loongson.cn>
> ---
Acked-by: Alan Stern <stern@rowland.harvard.edu>
> Change in v6:
> 1. Rework the commit log information.
> 2. Move the key change code after ohci_work in
> ohci_rh_suspend.
>
>
> drivers/usb/host/ohci-hub.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/usb/host/ohci-hub.c b/drivers/usb/host/ohci-hub.c
> index f474f2f..90cee19 100644
> --- a/drivers/usb/host/ohci-hub.c
> +++ b/drivers/usb/host/ohci-hub.c
> @@ -91,6 +91,9 @@ static int ohci_rh_suspend (struct ohci_hcd *ohci, int autostop)
> update_done_list(ohci);
> ohci_work(ohci);
>
> + /* All ED unlinks should be finished, no need for SOF interrupts */
> + ohci_writel(ohci, OHCI_INTR_SF, &ohci->regs->intrdisable);
> +
> /*
> * Some controllers don't handle "global" suspend properly if
> * there are unsuspended ports. For these controllers, put all
> --
> 1.8.3.1
>
prev parent reply other threads:[~2021-10-13 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 3:32 Yinbo Zhu
2021-10-13 14:06 ` Alan Stern [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=20211013140622.GA893308@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=patchwork-bot@kernel.org \
--cc=zhuyinbo@loongson.cn \
/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
all inboxes | Powered by JetHome®