On 08/17/2013 01:18 AM, Aaro Koskinen wrote: > Looking more into this (and after a failed testing attempt), I don't think > we can simply delete octeon-usb if we want to keep supporting Octeon: > there's also Octeon-specific registers of which the driver needs to > take care of before/while using DWC2 HW block. So migration to DWC2 is > not simply a driver change, we would still need some kind of octeon-hcd > glue for for it. I guess we should start converting octeon-usb to reuse > code from DWC2, but this won't happen overnight. If you look at musb / dwc3 they both have glue code around the USB IP core. Sebastian _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
