Hi, I spent some time on this issue. And it looks like the only possible solution to avoid USB disconnect from gadgetFs driver. In my trial, I avoided ep0_release/ep_release in every disconnect with function state update. With this CV passes without functionality impact.
I don't know what was the intention to keep functionfs_unbind and bind in every disconnect. But avoid this makes situation stable. Does anyone know why functionfs_unbind/bind is required in every disconnect?? Regrads, Roshan -----Original Message----- From: Felipe Balbi [mailto:ba...@ti.com] Sent: Saturday, December 14, 2013 1:27 AM To: Jhalani Roshan (EXT-MM/Bangalore) Cc: mzamp...@gmail.com; linux-usb@vger.kernel.org Subject: Re: gadgetfs USB2.0 Chapter 9 Tests: Test after "Addressed State" fails hi, On Fri, Dec 13, 2013 at 01:36:03PM +0000, roshan.jhal...@broadcom.com wrote: > 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. patches are welcome :-) -- balbi -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
