From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OMAP3: workaround for ARM Cortex-A8 erratum 725233
Date: Sun, 07 Feb 2010 08:45:36 -0600 [thread overview]
Message-ID: <4B6ED210.4050602@windriver.com> (raw)
In-Reply-To: <1265509186-14826-1-git-send-email-siarhei.siamashka@gmail.com>
Siarhei Siamashka wrote:
> 725233: PLD instructions executed with PLD data forwarding
> enabled can result in a processor deadlock
>
> Signed-off-by: Siarhei Siamashka <siarhei.siamashka@gmail.com>
Please add a detailed comment on the errata.
Also looks like this jumping to ROM code.
Can this be done without a ROM code call ?
Tom
> ---
> cpu/arm_cortexa8/omap3/board.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/cpu/arm_cortexa8/omap3/board.c b/cpu/arm_cortexa8/omap3/board.c
> index 2aa69b3..7b78fa4 100644
> --- a/cpu/arm_cortexa8/omap3/board.c
> +++ b/cpu/arm_cortexa8/omap3/board.c
> @@ -146,6 +146,12 @@ void setup_auxcr()
> __asm__ __volatile__("orr r0, r0, #1 << 5");
> /* SMI instruction to call ROM Code API */
> __asm__ __volatile__(".word 0xE1600070");
> + /* Set PLD_FWD bit in L2AUXCR (Cortex-A8 erratum 725233 workaround) */
> + __asm__ __volatile__("mov r12, #0x2");
> + __asm__ __volatile__("mrc p15, 1, r0, c9, c0, 2");
> + __asm__ __volatile__("orr r0, r0, #1 << 27");
> + /* SMI instruction to call ROM Code API */
> + __asm__ __volatile__(".word 0xE1600070");
> __asm__ __volatile__("mov r0, %0":"=r"(i));
> __asm__ __volatile__("mov r12, %0":"=r"(j));
> }
next prev parent reply other threads:[~2010-02-07 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 2:19 [U-Boot] [PATCH] OMAP3: workaround for ARM Cortex-A8 erratum 725233 Siarhei Siamashka
2010-02-07 2:19 ` [U-Boot] [PATCH] OMAP3: remove useless ASA bit from AUXCR Siarhei Siamashka
2010-02-07 14:45 ` Tom [this message]
2010-02-07 17:54 ` [U-Boot] [PATCH] OMAP3: workaround for ARM Cortex-A8 erratum 725233 Siarhei Siamashka
2010-02-08 13:15 ` Måns Rullgård
2010-02-08 15:27 ` Siarhei Siamashka
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=4B6ED210.4050602@windriver.com \
--to=tom.rix@windriver.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