OMAP baseline test results for v3.7-rc4

[khilman@deeprootsystems.com (Kevin Hilman)]

+Felipe, Venkat

Paul Walmsley <paul@pwsan.com> writes:

[...]

> Failing tests: needing investigation
> ------------------------------------
>

Here's another one for v3.7-rc4.

On all OMAP3 platforms I tested (3430/n900, 3530/Beagle, 3530/Overo,
3730/OveroSTORM, 3730/Beagle-xM), a system suspend (retention or off)
fails to wake up after a dynamic idle off-mode test (test script
below[1]).

I found that disabling MMC in the config made the tests pass again, so
then bisected it down to the commit below removing SYSCONFIG
accesses[2].  I haven't had the time to find out exactly the cause, but
clearly the code that was removed was doing something that hwmod is not
taking care of automatically.

Venkat, Felipe, could you please investigate this and hopefully get a
fix out for v3.7-rc?

Thanks,

Kevin


[1] Test for system suspend (retention) after off-idle

#!/bin/sh

echo 1 > /debug/pm_debug/enable_off_mode

echo 3000 > /sys/devices/platform/omap_uart.0/power/autosuspend_delay_ms
echo 3000 > /sys/devices/platform/omap_uart.1/power/autosuspend_delay_ms
echo 3000 > /sys/devices/platform/omap_uart.2/power/autosuspend_delay_ms
if [ -e /sys/devices/platform/omap_uart.3/power/autosuspend_delay_ms ]; then 
   echo 3000 > /sys/devices/platform/omap_uart.3/power/autosuspend_delay_ms
fi

sleep 5

echo -1 > /sys/devices/platform/omap_uart.0/power/autosuspend_delay_ms
echo -1 > /sys/devices/platform/omap_uart.1/power/autosuspend_delay_ms
echo -1 > /sys/devices/platform/omap_uart.2/power/autosuspend_delay_ms
if [ -e /sys/devices/platform/omap_uart.3/power/autosuspend_delay_ms ]; then 
   echo -1 > /sys/devices/platform/omap_uart.3/power/autosuspend_delay_ms
fi

echo 0 > /debug/pm_debug/enable_off_mode

rtcwake -m mem -s 1


[2]
commit 6c31b2150ff96755d24e0ab6d6fea08a7bf5c44c
Author: Venkatraman S <svenkatr@ti.com>
Date:   Wed Aug 8 14:26:52 2012 +0530

    mmc: omap_hsmmc: remove access to SYSCONFIG register
    
    SYSCONFIG register of HSMMC IP is managed by the omap hwmod
    abstraction layer. Resetting the IP and configuring the correct
    SYSCONFIG mode is centrally managed by hwmod.
    
    Remove code which manipulates IP reset and SYSCONFIG directly in
    the driver.
    
    Signed-off-by: Venkatraman S <svenkatr@ti.com>
    Acked-by: Felipe Balbi <balbi@ti.com>
    Signed-off-by: Chris Ball <cjb@laptop.org>