Hi Michael, On Thursday 24 January 2013 14:54:01 Michael Grzeschik wrote: > On Thu, Jan 24, 2013 at 12:02:12PM +0100, Laurent Pinchart wrote: > > On Thursday 24 January 2013 11:22:02 Michael Grzeschik wrote: > > > The current implementation of the composite framework connects the > > > gadget function to the device-controller at kernel boottime. > > > > > > It's possible that the userspace application, which handles the > > > enumeration requests of the gadget, starts with high latency when the > > > host did already gave up to detect the gadget. In that case the > > > gadget-application will not work in the first case. > > > > This shouldn't happen, as the UVC gadget driver should start disconnected > > (it calls usb_function_deactive() in uvc_function_bind()). If the host > > can enumerate the gadget before the application starts it would then > > likely be a device controller driver bug, not a UVC gadget driver bug. > > Unlikely this is not the case, as usb_gadget_probe_driver triggers an > usb_gadget_connect() right after driver->bind() was called. Indeed, for new-style UDC that's correct. Isn't that an issue with the framework ? I would expect gadget drivers to be able to start disconnected. > That is not a device controller bug. -- Regards, Laurent Pinchart -- 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
