Hi, >> 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 The fsg->state in gadget driver, is used for exception handling. Is there any variable to track the USB device state of Figure 9-1 of the USB 2.0 Spec? Now the gadget driver does not pass the "USB2.0 CV - Get Device Descriptor - Address State test". So i am trying to find more information. Thanks, victor -- 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
