Re: Problem in omap_pm_idle()

[Vivek Kutal <vivek.kutal@celunite.com>]

Tuukka.Tikkanen@elektrobit.com wrote:
> From: Vivek Kutal
> Subject: Problem in omap_pm_idle()
>   
>> Hi ,
>>        I was looking at omap_pm_idle() in omap1/pm.c , at the end
>>     
> there 
>   
>> is a call to omap_sram_suspend , shouldn't it be omap_sram_idle() ?
>>        and if CONFIG_OMAP_MPU_TIMER is set it sets  use_idlect1 = 
>> use_idlect1 & ~(1 << 9) ,  but it does not go into wait for interrupt.
>>        Can anyone please explain this ?
>>     
>
> The only real difference between suspend and idle sleep on omap1 is that
> for suspend peripheral devices are forcibly shut down. Also the idle
> sleep avoids turning off certain clock in some special cases. If there
> is no user or application activity, when everything is working as
> intended the hardware ends up into suspend-like state in idle sleep to
> conserve battery (with very quick recovery however), so the call is
> correct.
>
>   
So we should probably remove the omap_sram_push calls for omap_sram_idle 
from omap_pm_init , and its code from sleep.S...right ?

and what about the CONFIG_OMAP_MPU_TIMER problem ?
it should at least go in Wait for interrupt when mpu timer is 
used...right now it just exits from omap_pm_idle().

--
Thanks
Vivek Kutal