diff options
author | Paul Walmsley <paul@pwsan.com> | 2013-01-26 00:58:14 -0700 |
---|---|---|
committer | Paul Walmsley <paul@pwsan.com> | 2013-01-29 14:59:57 -0700 |
commit | f653b29825817a929a606726f03a04fcd0b2b566 (patch) | |
tree | 0f70038dcebbc4a0fb1ac95fd247cf9a3617fa7b /arch/arm/mach-omap2/powerdomain.h | |
parent | 53e1cb469e6cf353aa581e6b0a36cca359ecee25 (diff) | |
download | op-kernel-dev-f653b29825817a929a606726f03a04fcd0b2b566.zip op-kernel-dev-f653b29825817a929a606726f03a04fcd0b2b566.tar.gz |
ARM: OMAP2xxx: PM: clean up some crufty powerstate programming code
Don't attempt to put clockdomains to sleep; this should be handled by the
clock framework. It should be enough to program the next-power-state,
and then let the code in omap_pm_clkdms_setup() deal with the rest.
Start out by programming the MPU and CORE powerdomains to stay ON.
Then control the MPU and CORE powerdomain states directly in
omap2_enter_full_retention() and omap2_enter_mpu_retention(). Not the
most optimal way to do it, but certainly is the most conservative until
OMAP2xxx PM is working again.
Get rid of the open-coded PM_PWSTCTRL_MPU writes in
omap2_enter_mpu_retention(); use the powerdomain code instead.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>
Diffstat (limited to 'arch/arm/mach-omap2/powerdomain.h')
0 files changed, 0 insertions, 0 deletions