On Mon, Dec 11, 2017 at 03:15:37AM +0000, Yinbo Zhu wrote: > > > -----Original Message----- > From: Felipe Balbi [mailto:[email protected]] > Sent: Friday, December 08, 2017 6:44 PM > To: Greg Kroah-Hartman <[email protected]>; Yinbo Zhu > <[email protected]> > Cc: Mathias Nyman <[email protected]>; open list:DESIGNWARE USB3 DRD IP > DRIVER <[email protected]>; open list:DESIGNWARE USB3 DRD IP DRIVER > <[email protected]>; open list <[email protected]>; > Xiaobo Xie <[email protected]>; Jerry Huang <[email protected]>; Ran Wang > <[email protected]> > Subject: Re: [PATCH v2] usb: host: Implement workaround for Erratum A-009611 > > > >Hi, > > >Greg Kroah-Hartman <[email protected]> writes: > > On Fri, Dec 08, 2017 at 05:49:41PM +0800, [email protected] wrote: > >> From: "yinbo.zhu" <[email protected]> > >> > >> Description: This is a occasional problem where the software > > > > No need for a "Description:" word. That's just assumed here, right? > > I will remove "Description:" thanks. > >> 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. > > These configs is soc information, I don't enable it on these platform dts. > Although the erratum issue can't be reproduced.
I do not understand what this means, please explain it a bit better. thanks, greg k-h
