RE: MUSB regression in 2.6.31-rc6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > > @@ -13,6 +13,7 @@ config USB_MUSB_HDRC
> > >         select NOP_USB_XCEIV if ARCH_DAVINCI
> > >         select TWL4030_USB if MACH_OMAP_3430SDP
> > >         select NOP_USB_XCEIV if MACH_OMAP3EVM
> > > +       select NOP_USB_XCEIV if MACH_OMAP3_BEAGLE
> >
> > Shouldn't we be selecting TWL4030_USB if MACH_OMAP3_BEAGLE.
> > The beagleboard does use the PHY in the TWL4030, and not
> > a transparent PHY.
> >
> Could be. I have no very much idea of these :-)

Beagle has to use TWL4030_USB only and not NOP_USB_XCEIV. 

The NOP registration was removed from common file usb-musb.c
to board specific file because different board uses different transceiver.

>
> I happened to have both of these below enabled and 2.6.31-rc5 was still
> booting.
>
> CONFIG_TWL4030_USB=y
> CONFIG_NOP_USB_XCEIV=y
>
> But anyway, I don't get Beagle booting with 2.6.31-rc6 if I disable any
> of them and IRCC another oops will follow if both are disabled.

For Beagle;  only CONFIG_TWL4030_USB=y is required and should work with that alone.

> There's a patch from me adding back the twl4030_usb pdata to beagle
> board-file and another one from Paul which changed the defconfig.

It seems this dependency might be the cause why CONFIG_TWL4030_USB=y alone
didn't work as reported by Nikula.

> It should be easy to find on the archives. Eduardo Valentin reported
> that to me so I was asking him to test the stuff for me.


--
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

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux