This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP 35x - problem with restart/reboot in linux-02.01.01.08

Hi,

We're working with OMAP 3503. I have dropped the last version of linux we were using (linux-2.6.26.8 from GIT kernel tree) in favor of the latest TI's release (linux-02.01.01.08). But some things don't work better as I've expected from the new release.

The first thing is the restart procedure. On linux-2.6.26.8 from GIT kernel tree it was working fine, I mean the restart was successful pressing the "reset" button on our board. Here, in TI's release - linux-02.01.01.08 it doesn't work. The system hangs up both after pressing the "reset" button. The last message on the console is "Restarting system." The problem is the same I guess like in the previous TI distro (linux-0_9_7). The software "reboot" from the console works fine.

The next thing is abour the MMC and USB OTG drivers in TI's linux-02.01.01.08. In my opinion they work a little bit worse comparing to linux-2.6.26.8 from GIT kernel tree (in the linux-0_9_7 both MMC and USB Host/OTG drivers weren't too good). For example, in linux-02.01.01.08 sometimes I'm having troubles with read/write operations using MMC cards. In linux-2.6.26.8 it was great, no I/O errors, no "not enough space on drive" errors even if there was a LOT of free, unused disk space.

USB OTG in linux-2.6.26.8 works also great, I can plug a device which acts as a slave to OMAP. The driver on OTG port can see the device, powers it up (now OMAP acts as a host) and initializes proper device driver for the plugged hardware. In linux-02.01.01.08 both USB OTG and USB Host work good (we're using two USB ports), but if I try to plug an slave device to OTG port, yes the driver is able to see thats something was being plugged into OTG port, but the OTG driver doesn't power up the slave device (still OMAP tends to act as a slave device, not host) so the proper driver for the device cannot be loaded (USB OTG driver can't recognize the device plugged in is the slave device, OMAP keeps in device mode instead of switching to host mode).

 

Every tip how to fix the restart problem will be mostly appreciated. Also if someone is having (or had) similar problems with linux-02.01.01.08 with above issues (MMC, USB) please leave some hint.

 

Thank You.

Best regards,

Tomasz Kaczmarek.