On Tue, Sep 30, 2008 at 09:26:09AM -0700, Steve Sakoman wrote: > On Tue, Sep 30, 2008 at 6:05 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > > Let's plan on applying these tomorrow unless there are more comments. > > I'm seeing some issues on Overo when applying these patches. > > On a cold boot everything proceeds normally (including devices being > enumerated on the musb channel) until the kernel attempts to mount the > rootfs from mmc. At that point boot messages stop: > > mmc0: new high speed SD card at address 55ce > mmcblk0: mmc0:55ce SD02G 1921024KiB > mmcblk0:<7>mmc0: starting CMD18 arg 00000000 flags 000000b5 > p1 p2 > > At first I thought mmc support was broken and the system was hung. > But after a 10 - 20 second delay I noticed that approximately every 10 > seconds I get the following message: > > musb_h_tx_flush_fifo 124: Could not flush host TX fifo: csr: 000a > > After a few cycles of this the boot continues and completes normally, > but the musb port is now non-functional. > > If I do a reboot command or press the reset button, the overo reboots > without the above delays or error messages, however the musb port is > non-functional. > > It seems that something has gone awry in the twl4030 usb section, > since I get a functional system without these patches. Any > suggestions as to where I should begin looking to help debug this? remove the devices you have attached to musb port for now. musb shouldn't prevent these patches from being applied. As I said before, musb otg-host mode is not quite ok for omap3. I'm pretty sure we're gonna have a lot to patch in order to get it in good shape. A few patches are already coming from mainline btw. -- balbi -- 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
