On Fri, 1 Jul 2011, Benoit Cousson wrote: > From: Santosh Shilimkar <santosh.shilimkar@xxxxxx> > > 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@xxxxxx> > Signed-off-by: Rajendra Nayak <rnayak@xxxxxx> > [b-cousson@xxxxxx: Fix changelog typos] > Signed-off-by: Benoit Cousson <b-cousson@xxxxxx> > Cc: Paul Walmsley <paul@xxxxxxxxx> Thanks, this patch has been queued for 3.1 at git://git.pwsan.com/linux-2.6 in the 'hardware_workarounds_3.1' branch. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
