summaryrefslogtreecommitdiff
path: root/arch/arm/mach-omap2/omap-wakeupgen.c
diff options
context:
space:
mode:
authorSantosh Shilimkar <santosh.shilimkar@ti.com>2013-02-06 14:21:45 +0400
committerNishanth Menon <nm@ti.com>2014-09-08 20:38:41 +0400
commitd2136bce9db79f7d983f081c5d1b6e9359714dd6 (patch)
tree1c45d33cf0d57559201f9c40d1dbb0764d4f45c9 /arch/arm/mach-omap2/omap-wakeupgen.c
parenta89726d3b4cb81b033e34cc55974a33dab3279da (diff)
downloadlinux-d2136bce9db79f7d983f081c5d1b6e9359714dd6.tar.xz
ARM: OMAP5 / DRA7: PM: Set MPUSS-EMIF clock-domain static dependency
With EMIF clock-domain put under hardware supervised control, memory corruption and untraceable crashes are observed on OMAP5. Further investigation revealed that there is a weakness in the PRCM on this specific dynamic depedency. The recommendation is to set MPUSS static dependency towards EMIF clock-domain to avoid issues. This recommendation holds good for DRA7 family of devices as well. Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com> [rnayak@ti.com: DRA7] Signed-off-by: Rajendra Nayak <rnayak@ti.com> [nm@ti.com: conflict resolution, dra7] Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Kevin Hilman <khilman@linaro.org> Tested-by: Kevin Hilman <khilman@linaro.org>
Diffstat (limited to 'arch/arm/mach-omap2/omap-wakeupgen.c')
0 files changed, 0 insertions, 0 deletions