From: David Laight <David.Laight@ACULAB.COM>
To: 'Mathias Nyman' <mathias.nyman@linux.intel.com>,
alex zheng <tc0721@gmail.com>
Cc: Felipe Balbi <felipe.balbi@linux.intel.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"xiaowei.zheng@dji.com" <xiaowei.zheng@dji.com>
Subject: RE: BUG report: usb: dwc3: Link TRB triggered an intterupt without IOC being setted
Date: Wed, 25 Sep 2019 16:22:59 +0000 [thread overview]
Message-ID: <f5cd8ff1767c48a0bd86e743ae128b10@AcuMS.aculab.com> (raw)
In-Reply-To: <5431a9df-3816-b525-c3bc-4e7462d0f38f@linux.intel.com>
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)
next prev parent reply other threads:[~2019-09-25 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 8:34 BUG report: usb: dwc3: Link TRB triggered an intterupt without IOC being setted alex zheng
2019-09-23 5:36 ` Felipe Balbi
2019-09-23 7:08 ` alex zheng
2019-09-23 10:15 ` Mathias Nyman
[not found] ` <CADGPSwi87a5+3mCGAgptHgpBsQk9STQrEKs-kC6Nw55nPdRtOw@mail.gmail.com>
2019-09-25 14:48 ` Mathias Nyman
2019-09-25 16:22 ` David Laight [this message]
2019-09-26 5:45 ` Felipe Balbi
2019-09-26 8:21 ` Mathias Nyman
2019-09-26 10:38 ` alex zheng
[not found] ` <CADGPSwhCPvdu=KmQP6RHMJnh292UO0uBAt+KyJqqOWY5DWDc3w@mail.gmail.com>
2019-10-23 9:52 ` alex zheng
2019-10-23 10:01 ` Felipe Balbi
2019-10-25 8:44 ` alex zheng
2019-09-23 10:45 ` Felipe Balbi
2019-09-24 14:19 ` alex zheng
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=f5cd8ff1767c48a0bd86e743ae128b10@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=felipe.balbi@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=tc0721@gmail.com \
--cc=xiaowei.zheng@dji.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;
as well as URLs for NNTP newsgroup(s).