From: "Lu, Baolu" <baolu.lu@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
dheitmueller@kernellabs.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/1] usb: xhci: apply XHCI_AVOID_BEI quirk to Intel ValleyView and LynxPoint LP
Date: Thu, 12 Mar 2015 16:48:42 +0800 [thread overview]
Message-ID: <550152EA.7030203@linux.intel.com> (raw)
In-Reply-To: <20150312075433.GA32051@kroah.com>
On 03/12/2015 03:54 PM, Greg Kroah-Hartman wrote:
> On Thu, Mar 12, 2015 at 09:39:06AM +0800, Lu Baolu wrote:
>> When a device with an isochronous endpoint is plugged into the Intel
>> xHCI host controller, and the driver submits multiple frames per URB,
>> the xHCI driver will set the Block Event Interrupt (BEI) flag on all
>> but the last TD for the URB. This causes the host controller to place
>> an event on the event ring, but not send an interrupt. When the last
>> TD for the URB completes, BEI is cleared, and we get an interrupt for
>> the whole URB.
>>
>> However, under some Intel xHCI host controllers like ValleyView and
>> Lynx Point LP, if the event ring is full of events from transfers with
>> BEI set, a "Event Ring is Full" event will be posted to the last entry
>> of the event ring, but no interrupt is generated. Host will cease all
>> transfer and command executions and wait until software completes
>> handling the pending events in event ring. That means xHC stops but
>> event of "event ring is full" is not notified. As the result, the xHC
>> looks like dead to user.
>>
>> The patch is to apply XHCI_AVOID_BEI to Intel VallyView and Lynx Point
>> LP devices. And it should be backported to kernels as old as 3.0, that
>> contains the commit 69e848c2090a ("Intel xhci: Support EHCI/xHCI port
>> switching.")
>>
>> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
>> Cc: stable@vger.kernel.org
>> ---
>> drivers/usb/host/xhci-pci.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
>> index fd53c9e..5aa4893 100644
>> --- a/drivers/usb/host/xhci-pci.c
>> +++ b/drivers/usb/host/xhci-pci.c
>> @@ -40,6 +40,7 @@
>> #define PCI_DEVICE_ID_INTEL_CHERRYVIEW_XHCI 0x22b5
>> #define PCI_DEVICE_ID_INTEL_SUNRISEPOINT_H_XHCI 0xa12f
>> #define PCI_DEVICE_ID_INTEL_SUNRISEPOINT_LP_XHCI 0x9d2f
>> +#define PCI_DEVICE_ID_INTEL_VALLEYVIEW_XHCI 0x0f35
> Minor nit, you added a tab where the rest of the file was using a space
> :(
Yes, thanks for reminding.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2015-03-12 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 1:39 [PATCH 1/1] usb: xhci: apply XHCI_AVOID_BEI quirk to Intel ValleyView and LynxPoint LP Lu Baolu
2015-03-12 7:54 ` Greg Kroah-Hartman
2015-03-12 8:48 ` Lu, Baolu [this message]
2015-03-12 8:46 ` Mathias Nyman
2015-03-12 8:47 ` Lu, Baolu
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=550152EA.7030203@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dheitmueller@kernellabs.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).