From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yinbo Zhu <zhuyinbo@loongson.cn>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Patchwork Bot <patchwork-bot@kernel.org>
Subject: Re: [PATCH v4] usb: ohci: add check for host controller functional states
Date: Mon, 20 Dec 2021 16:59:13 +0100 [thread overview]
Message-ID: <YcCoUb7UBUErfvkm@kroah.com> (raw)
In-Reply-To: <1633957378-39631-1-git-send-email-zhuyinbo@loongson.cn>
On Mon, Oct 11, 2021 at 09:02:58PM +0800, Yinbo Zhu wrote:
> The usb states of ohci controller include UsbOperational, UsbReset,
> UsbSuspend and UsbResume. Among them, only the UsbOperational state
> supports launching the start of frame for host controller according
> the ohci protocol spec, but in S3 and S4 (suspend to memory/suspend
> to disk) press test procedure, it may happen that the start of
> frame was launched in other usb states and cause ohci works failed,
> that the phenomenon was hc will allways reproduce the SoF interrupt
> and consider that hc doesn't deal with the ed/td/done list in non-
> UsbOperational, and this patch was to add check for host controller
> functional states and if it is not UsbOperational state that need
> set INTR_SF in intrdisable register to ensure SOF Token generation
> was been disabled so that it can fix ohci SoF abnormally interrupt.
I do not understand this change. What commit is this fixing? What
devices today do not work with the code as-is?
>
> Signed-off-by: Yinbo Zhu <zhuyinbo@loongson.cn>
> ---
> Change in v4:
> Rework the commit log information.
> Remove the extra unnecessary blank line.
>
>
> drivers/usb/host/ohci-hcd.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/host/ohci-hcd.c b/drivers/usb/host/ohci-hcd.c
> index 1f5e693..4fd59fa 100644
> --- a/drivers/usb/host/ohci-hcd.c
> +++ b/drivers/usb/host/ohci-hcd.c
> @@ -879,7 +879,7 @@ static irqreturn_t ohci_irq (struct usb_hcd *hcd)
> {
> struct ohci_hcd *ohci = hcd_to_ohci (hcd);
> struct ohci_regs __iomem *regs = ohci->regs;
> - int ints;
> + int ints, ctl;
New line for a new variable please.
>
> /* Read interrupt status (and flush pending writes). We ignore the
> * optimization of checking the LSB of hcca->done_head; it doesn't
> @@ -969,9 +969,14 @@ static irqreturn_t ohci_irq (struct usb_hcd *hcd)
> * when there's still unlinking to be done (next frame).
> */
> ohci_work(ohci);
> - if ((ints & OHCI_INTR_SF) != 0 && !ohci->ed_rm_list
> - && ohci->rh_state == OHCI_RH_RUNNING)
> +
> + ctl = ohci_readl(ohci, ®s->control);
> + if (((ints & OHCI_INTR_SF) != 0 && !ohci->ed_rm_list
> + && ohci->rh_state == OHCI_RH_RUNNING) ||
> + ((ctl & OHCI_CTRL_HCFS) != OHCI_USB_OPER)) {
> ohci_writel (ohci, OHCI_INTR_SF, ®s->intrdisable);
> + (void)ohci_readl(ohci, ®s->intrdisable);
No need for (void).
thanks,
greg k-h
next prev parent reply other threads:[~2021-12-20 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 13:02 [PATCH v4] usb: ohci: add check for host controller functional states Yinbo Zhu
2021-12-20 15:59 ` Greg Kroah-Hartman [this message]
2021-12-20 21:35 ` Alan Stern
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=YcCoUb7UBUErfvkm@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=patchwork-bot@kernel.org \
--cc=stern@rowland.harvard.edu \
--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