tested this controller on the this and other PC with linux x86_32 and
windows, everything works ok
btw i have 2 similar controllers and the same problems
2017-01-14 16:53 GMT+03:00 c400 :
> a262eb551300 320471228 S Ci:4:001:0 s a3 00 0001 0004 4 <
> a262eb551300
On Sat, 14 Jan 2017, c400 wrote:
...
> a262eb5516c0 321863050 S Bo:4:002:2 -115 31 = 55534243 6e00
> 0010 8a28 0008 1008 00
> a262eb5516c0 321863062 C Bo:4:002:2 0 31 >
> a26333a3d3c0 321863073 S Bi:4:002:1 -115 4096 <
> a26333a3d3c0 321863103 C
a262eb551300 320471228 S Ci:4:001:0 s a3 00 0001 0004 4 <
a262eb551300 320471237 C Ci:4:001:0 0 4 = 03020100
a262eb551300 320471240 S Co:4:001:0 s 23 01 0010 0001 0
a262eb551300 320471242 C Co:4:001:0 0 0
a262eb551300 320471244 S Ci:4:001:0 s a3 00 0002 0004 4 <
When handing the SETUP packet by composite_setup(), we will release the
dwc->lock. If we get the 'USB_GADGET_DELAYED_STATUS' result from setup
function, which means we need to delay handling the STATUS phase.
But during the lock release period, maybe the request for handling delay
STATUS phase