From: Alan Stern <stern@rowland.harvard.edu>
To: David Jeffery <djeffery@redhat.com>
Cc: linux-usb@vger.kernel.org, Laurence Oberman <loberman@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Ewan Milne <emilne@redhat.com>,
apanagio@redhat.com, torez@redhat.com
Subject: Re: [PATCH] usb: ehci: Prevent missed ehci interrupts with edge-triggered MSI
Date: Wed, 14 Jul 2021 12:27:57 -0400 [thread overview]
Message-ID: <20210714162757.GD380727@rowland.harvard.edu> (raw)
In-Reply-To: <CA+-xHTGb73f_nCHg=D0qyFp2v-UaCpyisdbWvoUKTaVB077Zeg@mail.gmail.com>
On Wed, Jul 14, 2021 at 12:10:26PM -0400, David Jeffery wrote:
> On Wed, Jul 14, 2021 at 10:29 AM Alan Stern <stern@rowland.harvard.edu> wrote:
> >
> > Does this issue affect any other PCI-based host controller drivers?
> >
> > Alan Stern
> >
>
> Possibly. The uhci driver should have the same issue if hardware
> exists with it and has MSI for it. I suspect the ohci driver has a
> similar issue, but I'm not familiar enough with its interfaces and
> specification to say for sure.
Hmmm. I've never heard of an MSI implementation of either of those,
although it may be possible for OHCI. UHCI was used only by Intel and
one or two others; as far as I know none of them are producing those
controllers any more. Nowadays when people want to support USB-1.1
devices but not USB-3, they use an EHCI controller together with a
"rate-matching" hub, which avoids the need for any UHCI or OHCI
controller.
I was wondering more about dwc2 or other non-EHCI USB-2 controller
drivers.
Alan Stern
prev parent reply other threads:[~2021-07-14 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 14:03 [PATCH] usb: ehci: Prevent missed ehci interrupts with edge-triggered MSI David Jeffery
2021-07-14 14:27 ` Andy Shevchenko
2021-07-14 15:55 ` David Jeffery
2021-07-14 19:35 ` Andy Shevchenko
2021-07-14 14:29 ` Alan Stern
2021-07-14 16:10 ` David Jeffery
2021-07-14 16:27 ` 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=20210714162757.GD380727@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=andriy.shevchenko@linux.intel.com \
--cc=apanagio@redhat.com \
--cc=djeffery@redhat.com \
--cc=emilne@redhat.com \
--cc=linux-usb@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=torez@redhat.com \
/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