From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
Mathias Nyman <mathias.nyman@intel.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Should xhci_irq() call usb_hc_died()?
Date: Mon, 12 Dec 2016 10:43:31 +0200 [thread overview]
Message-ID: <87fultill8.fsf@linux.intel.com> (raw)
In-Reply-To: <20161210002616.GA8381@bhelgaas-glaptop.roam.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
Hi,
Bjorn Helgaas <helgaas@kernel.org> writes:
> Hi Mathias,
>
> ehci_irq(), ohci_irq(), fotg210_irq(), and oxu210_hcd_irq() contain code
> equivalent to this:
>
> status = ehci_readl(...);
> if (status == ~(u32) 0) {
> ...
> usb_hc_died(hcd);
> ...
> return IRQ_HANDLED;
> }
>
> xhci_irq() has a similar check, but does not call usb_hc_died():
>
> status = readl(...);
> if (status = 0xffffffff) {
> ...
> return IRQ_HANDLED;
> }
>
> Should xhci_irq() also call usb_hc_died()? Maybe there's some reason
> for it to be different than the others, but it wasn't obvious to this
> casual observer :)
you might just have fixed several bugs in dealing with a dead HC :-)
Can you provide a patch? (well, unless Mathias has a strong reason not
to call usb_hc_died(), of course).
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2016-12-12 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 0:26 Should xhci_irq() call usb_hc_died()? Bjorn Helgaas
2016-12-12 8:43 ` Felipe Balbi [this message]
2016-12-12 10:48 ` Mathias Nyman
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=87fultill8.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=stern@rowland.harvard.edu \
/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