From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: ls1021a: Ensure Generic Timer disabled before jumping into the OS
Date: Mon, 30 Nov 2015 09:00:15 -0800 [thread overview]
Message-ID: <565C809F.8080900@freescale.com> (raw)
In-Reply-To: <1438653337-47307-1-git-send-email-b18965@freescale.com>
On 08/03/2015 06:55 PM, Alison Wang wrote:
> 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>
> ---
Applied to fsl-qoriq master. Thanks.
York
prev parent reply other threads:[~2015-11-30 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 1:55 [U-Boot] [PATCH] arm: ls1021a: Ensure Generic Timer disabled before jumping into the OS Alison Wang
2015-08-14 16:12 ` York Sun
2015-08-17 7:42 ` [U-Boot] " Alexander Stein
2015-09-16 7:15 ` Huan Wang
2015-10-27 2:52 ` Huan Wang
2015-10-28 8:54 ` Alexander Stein
2015-10-28 15:20 ` Mark Rutland
2015-11-30 17:00 ` York Sun [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=565C809F.8080900@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox