On Mon, 24 Jun 2013, victor yeo wrote: > Hi, > > >> Ok, is the usb_ep_set_wedge routine not working? I can't see that in > >> the log file. > > > > It is not working. This can be seen in the usbmon log. > > I re-attach the usbmon log. If possible, please show me which line > indicates that usb_ep_set_wedge routine is not working, or how to look > for the clue. Is it from the control transfer line? Here's an example: f4148f80 3087777532 S Bo:1:011:1 -115 31 = 55534243 06000000 c0000000 8000061a 003f00c0 00000000 00000000 000000 f4148f80 3087777652 C Bo:1:011:1 0 31 > f14c5600 3087777676 S Bi:1:011:1 -115 192 < f14c5600 3087787651 C Bi:1:011:1 -121 16 = 0f000000 080a0400 ffff0000 ffffffff f4148f80 3087787674 S Bi:1:011:1 -115 13 < f4148f80 3087803018 C Bi:1:011:1 0 13 = 55534253 06000000 b0000000 00 The last line should have failed with a -32 error code, because the IN endpoint is supposed to be halted at this point. > >> I think the GET_STATUS request is not handled by the gadget driver. Isn't it so? > > > > That's right. Get-Status, Set-Feature, and Clear-Feature requests must > > be handled by the UDC driver. > > > > Alan Stern > > > > Should the UDC driver handle Get-Status before or after the call to fsg_setup()? For these requests, the UDC driver should not call fsg_setup() at all. It should handle the request entirely by itself. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
