public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, yinbo.zhu@nxp.com
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	"open list\:DESIGNWARE USB3 DRD IP DRIVER" 
	<linux-usb@vger.kernel.org>,
	"open list\:DESIGNWARE USB3 DRD IP DRIVER" 
	<linux-omap@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	xiaobo.xie@nxp.com, jerry.huang@nxp.com, ran.wang_1@nxp.com
Subject: Re: [PATCH v2] usb: host: Implement workaround for Erratum A-009611
Date: Fri, 08 Dec 2017 12:44:11 +0200	[thread overview]
Message-ID: <87vahhpkhw.fsf@linux.intel.com> (raw)
In-Reply-To: <20171208102111.GA16245@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 2516 bytes --]


Hi,

Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> On Fri, Dec 08, 2017 at 05:49:41PM +0800, yinbo.zhu@nxp.com wrote:
>> From: "yinbo.zhu" <yinbo.zhu@nxp.com>
>> 
>> Description: This is a occasional problem where the software
>
> No need for a "Description:" word.  That's just assumed here, right?
>
>> issues an End Transfer command while a USB transfer is in progress,
>> resulting in the TxFIFO  being flushed when the lower layer is waiting
>> for data,causing the super speed (SS) transmit to get blocked.
>> If the End Transfer command is issued on an IN endpoint to
>> flush out the pending transfers when the same IN endpoint
>> is doing transfers on the USB, then depending upon the timing
>> of the End Transfer (and the resulting internal FIFO flush),the
>> lower layer (U3PTL/U3MAC) could get stuck waiting for data
>> indefinitely. This blocks the transmission path on the SS, and no
>> DP/ACK/ERDY/DEVNOTIF packets can be sent from the device.
>> Impact: If this issue happens and the transmission gets blocked,
>> then the USB host aborts and resets/re-enumerates the device.
>> This unblocks the transmitt engine and the device functions normally.
>> 
>> Workaround: Software must wait for all existing TRBs to complete before
>> issuing End transfer command.
>> 
>> Configs Affected:
>> LS1088-48A-R1.0, LS2081A-R1.1, LS2088-48A-R1.0, LS2088-48A-R1.1,
>> LX2160-2120-2080A-R1.
>
> What are these Configs?  That doesn't seem to match up with anything
> that is in the kernel tree that I can see.
>
>> 
>> Signed-off-by: yinbo.zhu <yinbo.zhu@nxp.com>
>> ---
>>  drivers/usb/dwc3/core.c      |  3 +++
>>  drivers/usb/dwc3/core.h      |  3 +++
>>  drivers/usb/dwc3/host.c      |  3 +++
>>  drivers/usb/host/xhci-plat.c |  4 ++++
>>  drivers/usb/host/xhci.c      | 24 ++++++++++++++++++------
>>  drivers/usb/host/xhci.h      |  1 +
>>  6 files changed, 32 insertions(+), 6 deletions(-)
>> 
>> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
>> index 5cb3f6795b0b..071e7cea8cbb 100644
>> --- a/drivers/usb/dwc3/core.c
>> +++ b/drivers/usb/dwc3/core.c
>> @@ -1106,6 +1106,9 @@ static void dwc3_get_properties(struct dwc3 *dwc)
>>  
>>  	dwc->quirk_reverse_in_out = device_property_read_bool(dev,
>>  				"snps,quirk_reverse_in_out");

This was generated on vendor tree. This quirk doesn't exist in
dwc3. Also, update your tree and review MAINTAINERS file. It has been
almost 2 years since I left TI :-)

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-12-08 10:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171208094942.46748-1-yinbo.zhu@nxp.com>
2017-12-08 10:17 ` [PATCH v2] usb: host: Implement workaround for Erratum A-007463 Greg Kroah-Hartman
2017-12-11  2:26   ` Yinbo Zhu
2017-12-11  7:33     ` Greg Kroah-Hartman
2017-12-11  8:08       ` Yinbo Zhu
     [not found] ` <20171208094942.46748-2-yinbo.zhu@nxp.com>
2017-12-08 10:21   ` [PATCH v2] usb: host: Implement workaround for Erratum A-009611 Greg Kroah-Hartman
2017-12-08 10:44     ` Felipe Balbi [this message]
2017-12-11  3:15       ` Yinbo Zhu
2017-12-11  7:34         ` Greg Kroah-Hartman
2017-12-11  8:27           ` Yinbo Zhu
2017-12-11  8:51         ` Felipe Balbi
2017-12-12  7:09           ` Yinbo Zhu
2017-12-11  8:44     ` Yinbo Zhu

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=87vahhpkhw.fsf@linux.intel.com \
    --to=felipe.balbi@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jerry.huang@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=ran.wang_1@nxp.com \
    --cc=xiaobo.xie@nxp.com \
    --cc=yinbo.zhu@nxp.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