* Sebastian Reichel <sre@xxxxxxxxxx> [170518 10:25]: > Hi, > > On Thu, May 18, 2017 at 07:08:58AM -0700, Tony Lindgren wrote: > > * Sebastian Reichel <sre@xxxxxxxxxx> [170518 02:18]: > > > On Wed, May 17, 2017 at 03:59:21PM -0700, Tony Lindgren wrote: > > > > We can't just remove ohci-omap3 as that could make some people's > > > > systems unusable for keyboard and mouse. Let's print a warning for > > > > now, and then remove the driver in a year or so. > > > > > > I guess you could drop the driver and modify the Kconfig entry, > > > so that it selects USB_OHCI_HCD_PLATFORM? I just checked and > > > there are already a few examples of this in the USB host Kconfig :) > > > > Right but there's still nothing telling people to load ohci-platform > > instead of ohci-omap3 if we just remove ohci-omap3 without any warnings. > > Shouldn't the driver be loaded automatically due to the DT > compatible value? Doesn't that depend on a collection of user space software of varying quality and usability? :) But I think we can actually ohci-omap3 once the issues are sorted out. That's because for OHCI omaps need an OHCI PHY. In most cases there is just EHCI PHY and an external hub is needed. I'll do some more testing. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
