OMAP4: clock: Keep GPMC clocks always enabled and hardware managed.
authorSantosh Shilimkar <santosh.shilimkar@ti.com>
Mon, 27 Jun 2011 23:30:26 +0000 (16:30 -0700)
committerVolodymyr Riazantsev <x0153367@ti.com>
Wed, 29 Jun 2011 13:40:54 +0000 (08:40 -0500)
commitaca0ad5b518cfee74dcbdc1c0f3c2bd25aa7560a
treebd7ef78f98aa5a2a7bb072a3546c5d6191a811f5
parent48753bc5d42ce7e40fb05d365434ceac811136c6
OMAP4: clock: Keep GPMC clocks always enabled and hardware managed.

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 is't a 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.

Change-Id: If1641d30d6ad4c4429b2a5a8c613853a4ed325c1
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Kevin Hilman <khilman@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>
Cc: Benoit Cousson <b-cousson@ti.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Signed-off-by: Volodymyr Riazantsev <x0153367@ti.com>
arch/arm/mach-omap2/clock44xx_data.c