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 v2] usb: ohci: add check for start frame in host controller functional states
Date: Wed, 29 Sep 2021 10:59:05 -0400 [thread overview]
Message-ID: <20210929145905.GA428239@rowland.harvard.edu> (raw)
In-Reply-To: <1632910167-23554-1-git-send-email-zhuyinbo@loongson.cn>
On Wed, Sep 29, 2021 at 06:09:27PM +0800, Yinbo Zhu wrote:
> The pm states of ohci controller include UsbOperational, UsbReset, UsbSuspend
Those aren't really PM states. The specification calls them "USB
states".
> , and UsbResume. Among them, only the UsbOperational state supports launching
--^
This comma should come directly after the word "launching", with no
space in between.
> the start frame for host controller according the ohci protocol spec, but in
> S3/S4 press test procedure, it may happen that the start frame was launched
What is the S3/S4 press test? I don't recall hearing of it before.
> in other pm states and cause ohci works abnormally then kernel will allways
> report rcu CallTrace. This patch was to add check for start frame in host
> controller functional states for fixing above issue.
The patch doesn't check for start of frames, that is, it doesn't check
the INTR_SF bit in the intrstatus register. Instead it checks whether
controller is in the UsbOperational state. And the patch also sets
INTR_SF in the intrdisable register -- you do not mention this in the
description.
> Signed-off-by: Yinbo Zhu <zhuyinbo@loongson.cn>
> ---
> Change in v2:
> Revise the punctuation.
>
> drivers/usb/host/ohci-hcd.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/usb/host/ohci-hcd.c b/drivers/usb/host/ohci-hcd.c
> index 1f5e693..f0aeae5 100644
> --- a/drivers/usb/host/ohci-hcd.c
> +++ b/drivers/usb/host/ohci-hcd.c
> @@ -881,6 +881,13 @@ static irqreturn_t ohci_irq (struct usb_hcd *hcd)
> struct ohci_regs __iomem *regs = ohci->regs;
> int ints;
>
> + ints = ohci_readl(ohci, ®s->control);
> +
> + if ((ints & OHCI_CTRL_HCFS) != OHCI_USB_OPER) {
> + ohci_writel(ohci, OHCI_INTR_SF, ®s->intrdisable);
> + (void)ohci_readl(ohci, ®s->intrdisable);
> + }
The driver is already supposed to prevent this problem by writing the
OHCI_INTR_SF flag to the intrdisable register when start-of-frame
interrupts aren't needed. Maybe what you should do is change this code
lower down in ohci_irq():
if ((ints & OHCI_INTR_SF) != 0 && !ohci->ed_rm_list
&& ohci->rh_state == OHCI_RH_RUNNING)
ohci_writel (ohci, OHCI_INTR_SF, ®s->intrdisable);
by getting rid of the test for OHCI_RH_RUNNING.
Alan Stern
> +
> /* Read interrupt status (and flush pending writes). We ignore the
> * optimization of checking the LSB of hcca->done_head; it doesn't
> * work on all systems (edge triggering for OHCI can be a factor).
> --
> 1.8.3.1
>
next parent reply other threads:[~2021-09-29 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1632910167-23554-1-git-send-email-zhuyinbo@loongson.cn>
2021-09-29 14:59 ` Alan Stern [this message]
2021-09-29 15:01 ` Alan Stern
2021-10-08 7:18 ` zhuyinbo
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=20210929145905.GA428239@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®