Hi, (avoid top-posting and break your lines at 80-chars) On Mon, Dec 23, 2013 at 08:29:01AM +0000, roshan.jhalani@xxxxxxxxxxxx wrote: > 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?? Michal ? > > Regrads, > Roshan > > -----Original Message----- > From: Felipe Balbi [mailto:balbi@xxxxxx] > Sent: Saturday, December 14, 2013 1:27 AM > To: Jhalani Roshan (EXT-MM/Bangalore) > Cc: mzamponi@xxxxxxxxx; linux-usb@xxxxxxxxxxxxxxx > 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.jhalani@xxxxxxxxxxxx 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 -- balbi
Attachment:
signature.asc
Description: Digital signature
