From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OMAP3: set L1NEON bit in aux control register
Date: Sat, 15 Nov 2008 06:52:40 +0100 [thread overview]
Message-ID: <491E63A8.5090206@googlemail.com> (raw)
In-Reply-To: <1226703695-14978-1-git-send-email-mans@mansr.com>
Mans Rullgard wrote:
> This is required to work around ARM erratum 621766, affecting
> Cortex-A8 r1p0-3:
>
> When a sequence of Neon load instructions is intermixed with several
> branches, some of which are mispredicted, it is possible for the
> processor to deadlock due to Neon loads on the speculative path not
> being properly flushed from the Neon load queue.
>
> Signed-off-by: Mans Rullgard <mans@mansr.com>
Acked-by: Dirk Behme <dirk.behme@gmail.com>
---
Jean-Christophe: This is for u-boot-arm/omap3, so please read the
subject as "[PATCH-OMAP3] OMAP3: ..."
> ---
> cpu/arm_cortexa8/omap3/board.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/cpu/arm_cortexa8/omap3/board.c b/cpu/arm_cortexa8/omap3/board.c
> index 90809a6..7c2a7ea 100644
> --- a/cpu/arm_cortexa8/omap3/board.c
> +++ b/cpu/arm_cortexa8/omap3/board.c
> @@ -139,6 +139,8 @@ void setup_auxcr()
> __asm__ __volatile__("mrc p15, 0, r0, c1, c0, 1");
> /* Enabling ASA */
> __asm__ __volatile__("orr r0, r0, #0x10");
> + /* Enable L1NEON */
> + __asm__ __volatile__("orr r0, r0, #1<<5");
> /* SMI instruction to call ROM Code API */
> __asm__ __volatile__(".word 0xE1600070");
> __asm__ __volatile__("mov r0, %0":"=r"(i));
prev parent reply other threads:[~2008-11-15 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 23:01 [U-Boot] [PATCH] OMAP3: set L1NEON bit in aux control register Mans Rullgard
2008-11-15 5:52 ` Dirk Behme [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=491E63A8.5090206@googlemail.com \
--to=dirk.behme@googlemail.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