]> git.ipfire.org Git - thirdparty/u-boot.git/commit
arm: ls1021a: Ensure Generic Timer disabled before jumping into the OS
authorAlison Wang <b18965@freescale.com>
Tue, 4 Aug 2015 01:55:37 +0000 (09:55 +0800)
committerYork Sun <yorksun@freescale.com>
Mon, 30 Nov 2015 16:53:01 +0000 (08:53 -0800)
commita1399534f103883908a3a826c9f0505b92b0c75e
tree36a1bbbfdcc33f7259acbb653504c75a305cd2f9
parent2b714cfad4bb75e9be394de36929ef5c79ce17bb
arm: ls1021a: Ensure Generic Timer disabled before jumping into the OS

This patch addresses a problem mentioned recently on this mailing list:
[1].

In that posting a LS1021 based system was locking up at about 5 minutes
after boot,but the problem was mysteriously related to the toolchain
used for building u-boot.Debugging the problem reveals a stuck
interrupt 29 on the GIC.

It appears Freescale's LS1021 support in u-boot erroneously sets the
64-bit ARM generic PL1 physical time CompareValue register to all-ones
with a 32-bit value.This causes the timer compare to fire 344 seconds
after u-boot configures it.Depending on how fast u-boot gets the
kernel booted,this amounts to about 5-minutes of Linux uptime before
locking up.

Apparently the bug is masked by some toolchains. Perhaps this is
explained by default compiler options, word sizes, or binutils versions.

To fix the above issue, the generic physical timer is disabled
before jumping to the OS.

[1]
https://lists.yoctoproject.org/pipermail/meta-freescale/2015-June/014400.html

Signed-off-by: Chris Kilgour <techie@whiterocker.com>
Signed-off-by: Alison Wang <alison.wang@freescale.com>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: York Sun <yorksun@freescale.com>
arch/arm/cpu/armv7/ls102xa/cpu.c