On Thu, 28 Feb 2013, Venu Byravarasu wrote: > To clear any configurations made by U-Boot on Tegra USB controller, > reset it before init in probe. > > Signed-off-by: Venu Byravarasu <vbyravarasu@xxxxxxxxxx> > --- > When U-Boot configures a Tegra USB controller in device mode and if the EHCI > driver of kernel tries to set it to HOST mode, message "irq 52: nobody cared" > appears and IRQ gets disabled. > > This issue was initially reported with: http://marc.info/?l=linux-tegra&m=136110175423601&w=2 > > To avoid such issues, due to configurations made by U-Boot driver, reset the > Tegra USB controller, before configuring it by kernel. Does the Tegra platform use shared interrupts? If it does, what happens if the IRQ is enabled and in use by another device before ehci-tegra resets the USB controller? Does the unwanted interrupt occur only when the controller is switched to host mode? If not, it seems to me this reset belongs in the platform code, not in the glue layer. If yes, the reset belongs somewher before the controller is switched -- where does that occur? Alan Stern -- 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
