From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: liangshengjun <liangshengjun@hisilicon.com>,
Alan Stern <stern@rowland.harvard.edu>
Cc: "stable\@vger.kernel.org" <stable@vger.kernel.org>,
"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: 答复: make a confirm for [usb: dwc3: gadget: skip Set/Clear Halt when invalid]
Date: Fri, 29 Jun 2018 09:21:14 +0300 [thread overview]
Message-ID: <874lhmf6zp.fsf@linux.intel.com> (raw)
In-Reply-To: <84923CA334DF85428B9ADCEC0F3CE864BA1EA4@dggemm510-mbx.china.huawei.com>
(no top-posting!!)
liangshengjun <liangshengjun@hisilicon.com> writes:
> Hi balbi,
>
> It means that the mainline keep checking stall status first before
> handle clear-halt request? as usb spec, it's actually okay to send
> Clear Halt at any time. But dwc3 core hanging with macOS adb
> application, so I think there is other rootcase why dwc3 hanging , and
> current patch just for avoid this case. Right?
that's correct. There's another problem happening that causes dwc3 to
hang. I guess I'll just revert that patch since it causes more problems
than solve.
> If someday WindonwPC/LINUX PC meet this case again liked my case,
> would you plan to revert it ? or other plan ?
I'll just revert it.
--
balbi
next prev parent reply other threads:[~2018-06-29 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <84923CA334DF85428B9ADCEC0F3CE864BA1492@dggemm510-mbx.china.huawei.com>
2018-06-21 9:42 ` make a confirm for [usb: dwc3: gadget: skip Set/Clear Halt when invalid] Felipe Balbi
2018-06-21 15:29 ` Alan Stern
2018-06-25 7:47 ` Felipe Balbi
2018-06-29 2:10 ` 答复: " liangshengjun
2018-06-29 6:21 ` Felipe Balbi [this message]
2018-11-16 23:54 ` Thinh Nguyen
2018-11-19 6:35 ` Felipe Balbi
2018-06-25 9:37 liangshengjun
2018-06-25 9:43 ` Felipe Balbi
2018-06-26 10:09 ` 答复: " liangshengjun
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=874lhmf6zp.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=liangshengjun@hisilicon.com \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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).