diff options
| author | Girish S Ghongdemath <girishsg@ti.com> | 2011-07-21 19:48:32 -0500 |
|---|---|---|
| committer | Iliyan Malchev <malchev@google.com> | 2011-07-21 22:48:39 -0700 |
| commit | 97c4e420514c12e5214a9fc3a9f5bb6797cafcc6 (patch) | |
| tree | 733b26649d0b5ecde0222f2199617b3758db6160 /drivers/ps3 | |
| parent | 2ccbb6b164520374e41f649d3e8049ffea38d150 (diff) | |
| download | kernel_samsung_tuna-97c4e420514c12e5214a9fc3a9f5bb6797cafcc6.zip kernel_samsung_tuna-97c4e420514c12e5214a9fc3a9f5bb6797cafcc6.tar.gz kernel_samsung_tuna-97c4e420514c12e5214a9fc3a9f5bb6797cafcc6.tar.bz2 | |
OMAP4: PM: do omap_device_idle for ISS and fdif
omap_device_shutdown should be called only when module is getting
unloaded. Else there can be a chance when standby is getting asserted
and forceidle is applied on the module causing interface to lock up
on next access.
ISS hang: device_shutdown was setting forceidle, this was unconditionally
putting the interface to idle. The recommended setting is to call for device_idle
which will set smartstdby/smartidle. This makes sure that all the submodules of ISS asserts
Mstadby and once ISS acks back interface will be safe to idle.
Do omap_device_idle for fdif as well.
Change-Id: I94fee16ccc66c60de8c6060745aa1f92c0045dbc
Signed-off-by: Girish S G <girishsg@ti.com>
Diffstat (limited to 'drivers/ps3')
0 files changed, 0 insertions, 0 deletions