RE: Problem in omap_pm_idle()

Tuukka.Tikkanen
2007-09-19T12:58:11Z

[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]

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.

Tuukka

----------------------------------------------------------------
Please note: This e-mail may contain confidential information
intended solely for the addressee. If you have received this
e-mail in error, please do not disclose it to anyone, notify
the sender promptly, and delete the message from your system.
Thank you.

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]