summaryrefslogtreecommitdiff
path: root/arch/arm/mach-omap2/clock44xx_data.c
diff options
context:
space:
mode:
authorSantosh Shilimkar <santosh.shilimkar@ti.com>2011-07-10 06:42:59 +0400
committerPaul Walmsley <paul@pwsan.com>2011-07-10 06:42:59 +0400
commita57341f780660800e1463eaedb80ed152ad6b5de (patch)
treecda1eb63b8be847a0baf0a9545263b174c64f681 /arch/arm/mach-omap2/clock44xx_data.c
parent93cac2ad0f9459422d0af79b6937d6e83ed3aec9 (diff)
downloadlinux-a57341f780660800e1463eaedb80ed152ad6b5de.tar.xz
OMAP4: powerdomain data: Remove unsupported MPU powerdomain state
On OMAP4430 devices, because of boot ROM code bug, MPU OFF state can't be attempted independently. When coming out of MPU OFF state, ROM code disables the clocks of IVAHD, TESLA which is not desirable. Hence the MPU OFF state is not usable on OMAP4430 devices. OMAP4460 onwards, MPU OFF state will be descoped completely because the DDR firewall falls in MPU power domain. When the MPU hit OFF state, DDR won't be accessible for other initiators. The deepest state supported is open switch retention (OSWR) just like CORE and PER PD on OMAP4430. So in summary MPU power domain OFF state is not supported on OMAP4 and onwards designs. Thanks to new PRCM design, device off mode can still be achieved with power domains hitting OSWR state. Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com> Signed-off-by: Rajendra Nayak <rnayak@ti.com> [b-cousson@ti.com: Fix changelog typos] Signed-off-by: Benoit Cousson <b-cousson@ti.com> Signed-off-by: Paul Walmsley <paul@pwsan.com>
Diffstat (limited to 'arch/arm/mach-omap2/clock44xx_data.c')
0 files changed, 0 insertions, 0 deletions