summaryrefslogtreecommitdiffstats
path: root/firmware/cis/NE2K.cis.ihex
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2016-06-22 10:59:39 +0200
committerTony Lindgren <tony@atomide.com>2016-06-23 07:55:51 +0200
commit0573b957fc21c6a6cee01fdb08c1f7ce556afbac (patch)
tree26c28496da0cb970e04f01f9520758313c39ed63 /firmware/cis/NE2K.cis.ihex
parentARM: OMAP4+: Initialize SAR RAM base early for proper CPU1 reset for kexec (diff)
downloadlinux-0573b957fc21c6a6cee01fdb08c1f7ce556afbac.tar.xz
linux-0573b957fc21c6a6cee01fdb08c1f7ce556afbac.zip
ARM: OMAP4+: Prevent CPU1 related hang with kexec
Kexec booted kernels on omap4 will hang early during the boot if the booted kernel is different version from the previous kernel. This is because the previous kernel may have configured low-power mode using CPU1_WAKEUP_NS_PA_ADDR. In that case it points to the previous kernel's omap4_secondary_startup(), and CPU1 can be in low power mode from the previous kernel. When the new kernel configures the CPU1 clockdomain, CPU1 can wake from low power state prematurely during omap44xx_clockdomains_init() running random code. Let's fix the issue by configuring CPU1_WAKEUP_NS_PA_ADDR before we call omap44xx_clockdomains_init(). Note that this is very early during the init, and we will do proper CPU1 reset during SMP init a bit later on in omap4_smp_prepare_cpus(). And we need to do this when SMP is not enabled as the previous kernel may have had it enabled. Acked-by: Santosh Shilimkar <ssantosh@kernel.org> Tested-by: Keerthy <j-keerthy@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'firmware/cis/NE2K.cis.ihex')
0 files changed, 0 insertions, 0 deletions