* Gupta, Ajay Kumar <ajay.gupta@xxxxxx> [100706 10:17]: > > As musb controllers are quite different between OMAPs and AM35x so it > would be difficult in terms of software maintenance with such approach. Hmm, this is all pretty standard stuff.. > Some of the major changes in AM35x are, > - Has builtin USB PHY Register the PHY from platform data. > - It doesn't use Mentor DMA but uses CPPI4.1 DMA Register DMA functions from platform data. > - Has set of wrapper register which are not present on OMAPs. Yeah tusb6010 has the same problem, but that's already dealt with I believe. > - Doesn't have SYSCONFIG registers which are present on OMAPs. > - Has bytewise read limitation which is not applicable to OMAPs. Sounds like this has been mostly dealt with already with tusb6010. > Musb on AM35x is actually quite similar to musb on DA8xx family of > Devices. > > I can update the patches to use USB_MUSB_AM35X config within > drivers/usb/musb/ but that would still not be able to compile in > Both omapx and am35x stuff in single binary. Sounds like we should first fix thing before adding new code that will make fixing the basic issues harder. Tony -- 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