On Fri, 3 Sep 2010, [utf-8] MichaÅ? Nazarewicz wrote: > >> I've noticed that you've added priv. I would also add some kind of name or > >> (name, id) pair. Both of those could be a way to allow several UDCs to work. > >> usb_gadget_register() (or usb_gadget_probe() in next) would take the first > >> available UDC but usb_gadget_probe_named() could be added which would allow > >> to specify UDC by name. > > On Fri, 03 Sep 2010 05:49:25 +0200, David Brownell <david-b@xxxxxxxxxxx> wrote: > > NAK let's just not go there. We want gadget drivers > > to be hardware-neutral, not hardware-dependent. > > I was thinking more along the way of gadgets having a module parameter > like udc=<name>. With composite it would be like 5 lines of code to > implement and user space would be able to specify that the gadget it is > now loading should go with this UDC. > > Just my thoughts. Why would the user want to tell the gadget driver which UDC to bind to? There can be only one UDC active at any time. Alan Stern -- 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
