I've been implementing a UDC driver for the on-board UDC of various SuperH devices. I have now got the device to enumerate using Gadget Zero but this has exposed some problems with the gadget driver framework when used with the SuperH UDC.
The SuperH UDC is less flexible than the other supported UDCs and it also does more in hardware without letting the driver software know. The main issues are:
It only supports one configuration (configuration 1). To handle that I have modified Gadget Zero to compile as either loopback or source sink. This isn't a major problem.
More seriously several control commands are automatically processed by the hardware and the software is not informed (no interrupt is generated). These commands are: Clear Feature, Get Configuration, Set Configuration, Get Interface, Get Status, Set Address, Set Feature, Set Interface.
The current gadget drivers seem to rely on some of these commands being passed on by the UDC driver, but in the case of the SuperH UDC this is not possible.
Any suggestions for a clean way to get round this problem?
Thanks
Julian Back
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
