RE: BUG report: usb: dwc3: Link TRB triggered an intterupt without IOC being setted

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Mathias Nyman
> Sent: 25 September 2019 15:48
> 
> On 24.9.2019 17.45, alex zheng wrote:
> > Hi Mathias,
...
> Logs show your transfer ring has four segments, but hardware fails to
> jump from the last segment back to first)
> 
> Last TRB (LINK TRB) of each segment points to the next segment,
> last segments link trb points back to first segment.
> 
> In your case:
> 0x1d117000 -> 0x1eb09000 -> 0x1eb0a000 -> 0x1dbda000 -> (back to 0x1d117000)
> 
> For some reason your hardware doesn't treat the last TRB at the last segment
> as a LINK TRB, instead it just issues a transfer event for it, and continues to
> the next address instead of jumping back to first segment:

That could be a cache coherency (or flushing (etc)) issue.

>> This is our self-design platform (ARM v7 cpu core  with synopsys DWC USB3.0 controller).
Or maybe your hardware is just getting some of the memory accesses wrong?

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux