Hi Macro, We have observed same issue and reason for this issue is reset_config which triggers complete USB disconnect from F_FS. For SET_CONFIG(Config#0) there is no need to do USB Disconnect. This seems to be bottleneck issue for USB compliance. I believe this issue should be addressed by GadgetFS driver. Regards, Roshan -----Original Message----- From: linux-usb-owner@xxxxxxxxxxxxxxx [mailto:linux-usb-owner@xxxxxxxxxxxxxxx] On Behalf Of Marco Johannes Sent: Friday, December 13, 2013 6:56 PM To: linux-usb@xxxxxxxxxxxxxxx Subject: gadgetfs USB2.0 Chapter 9 Tests: Test after "Addressed State" fails Hello! I am new to this group and hope you can help me out. I am on an embedded board with an ARM cortex a5 and using gadgetfs. An Application that is derived from the usb.c example is running on it while the board is connected to a PC with the USB 2.0 Command Verifier. I am quite new to development with usb. When I run all the Chapter 9 tests, the "Device Descriptor Test - Configured State" and the "Device Descriptor Test - Addressed State" are passed while the "Interface Association Descriptor Test" and all the following tests fail. I found out that in "Interface Association Descriptor Test" the open() of the endpoint fails as well as the read() of the filedescriptor after handling the "USB_REQ_SET_CONFIGURATION" in this line: /* ... ack (a write would stall) */ status = read (fd, &status, 0); if (status) perror ("\t\tack SET_CONFIGURATION"); return; The print out of the error message is "Identifier removed". I noticed that when I leave out all the "Adressed state" Tests, my Tests would all pass. As I mentioned, I'm new to USB developing and maybe there's no way to achieve Chapter 9 conformity with GadgetFS or there's a known bug? Thanks for any additional info! -- 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 -- 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
