From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: alex zheng <tc0721@gmail.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
David Laight <David.Laight@aculab.com>
Cc: "linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
"xiaowei.zheng\@dji.com" <xiaowei.zheng@dji.com>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Subject: Re: BUG report: usb: dwc3: Link TRB triggered an intterupt without IOC being setted
Date: Wed, 23 Oct 2019 13:01:52 +0300 [thread overview]
Message-ID: <87v9sfixv3.fsf@gmail.com> (raw)
In-Reply-To: <CADGPSwiCY9=kUpKmcUwAhvCHmvGDSrxoBXEkzgQpEpiakKEv6A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
Hi,
(please don't top-post)
alex zheng <tc0721@gmail.com> writes:
> Hi, all
>
> We found that this is a known issue of synopsys DWC3 USB controller,
> when the PARKMODE_SS of DWC3 is enable, the controller may hang or do
> wrong TRB schedule in some heavy load conditions.
>
> Setting DISABLE_PARKMODE_SS to 1 can work around this bug.
Is this something that affects some versions but not others? If the
case, we should teach the driver to handle this based on a revision
check.
cheers
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-10-23 10:02 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
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 [this message]
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=87v9sfixv3.fsf@gmail.com \
--to=felipe.balbi@linux.intel.com \
--cc=David.Laight@aculab.com \
--cc=Thinh.Nguyen@synopsys.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).