Hi,
Thinh Nguyen writes:
>>> 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
Hi Felipe,
On 6/28/2018 11:24 PM, Felipe Balbi wrote:
> (no top-posting!!)
>
> liangshengjun 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
(no top-posting!!)
liangshengjun 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
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
After merge the patch
[PATCH] usb: dwc3: gadget: properly increment dequeue pointer on,
fixed the case.
Thank you so much.
Liang Shengjun
-邮件原件-
发件人: Felipe Balbi [mailto:felipe.ba...@linux.intel.com]
发送时间: 2018年6月25日 17:43
收件人: liangshengjun
抄送: sta...@vger.kernel.org;
