Felipe Balbi wrote:
So that should work IMHO. What we miss is the information which function
driver to load but we are talking about UDC (device) driver atm.
What we miss is information on to which UDC controller bind the gadget
driver but that's the same we have today, it just binds to the first
(currently only) UDC available.
We could take this information from DT/platform_data but this information
isn't static i.e. people may load to use mass storage by loading the
driver and then switch to a serial gadget just by replacing the gadget.
So in the end it is complete configurable by the user. For this kind of
things we have sysfs.
echo "mass_storage" > /sysfs/.../udc0/function
looks usable. Maybe a few other files for configuration and one for
bind / unbind.
Sebastian
--
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
