On Fri, 1 Jul 2011, Benoit Cousson wrote: > From: Santosh Shilimkar <[email protected]> > > On OMAP4, CPU accesses on unmapped addresses are redirected to GPMC by > L3 interconnect. Because of CPU speculative nature, such accesses are > possible which can lead to indirect access to GPMC and if it's clock is > not running, it can result in hang/abort on the platform. > > Above makes access to GPMC unpredictable during the execution, so it's > module mode needs to be kept under hardware control instead of software > control. > Since the auto gating is supported for GPMC, there isn't any power impact > because of this change. > > The issue was un-covered with security middleware running along with HLOS. > In this case GPMC had a valid MMU descriptor on secure side where as HLOS > didn't map the GMPC because it isn't being used. > > Signed-off-by: Santosh Shilimkar <[email protected]> > [[email protected]: Update subject and fix typos in the changelog] > Signed-off-by: Benoit Cousson <[email protected]> > Cc: Kevin Hilman <[email protected]> > Cc: Paul Walmsley <[email protected]> > Cc: Rajendra Nayak <[email protected]>
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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
