On Fri, 9 Sep 2016, Tony Lindgren wrote: > With LPAE config we don't have omap3 or omap4 selected for > omap5 variants. > > Signed-off-by: Tony Lindgren <[email protected]> > --- > drivers/usb/host/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig > --- a/drivers/usb/host/Kconfig > +++ b/drivers/usb/host/Kconfig > @@ -472,7 +472,7 @@ config USB_OHCI_HCD_AT91 > > config USB_OHCI_HCD_OMAP3 > tristate "OHCI support for OMAP3 and later chips" > - depends on (ARCH_OMAP3 || ARCH_OMAP4) > + depends on (ARCH_OMAP3 || ARCH_OMAP4 || SOC_OMAP5) > default y > ---help--- > Enables support for the on-chip OHCI controller on
Acked-by: Alan Stern <[email protected]> You know, as far as I can tell the only thing that is OMAP-specific about the ohci-omap3 driver is the initialization of OHCI_CTRL_RWC. This could be added to the platform data or the DT bindings, after which this driver wouldn't be needed at all -- the ohci_platform driver would work. Does this seem reasonable? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
