From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx5: Add workaround for ARM erratum ID 468414
Date: Wed, 09 May 2012 11:36:30 +0200 [thread overview]
Message-ID: <4FAA3A9E.2090506@denx.de> (raw)
In-Reply-To: <1336424160-17256-1-git-send-email-festevam@gmail.com>
On 07/05/2012 22:56, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Add the software workaround for ARM erratum ID 468414.
>
> According to mx53/mx51 errata document:
>
> "ENGcm11133 - ARM: NEON load data can be incorrectly forwarded to a
> subsequent request
>
> Description:
>
> Under very specific set of conditions, data from a Neon load request can be incorrectly forwarded
> to a subsequent, unrelated memory request.
> The conditions are as follows:
> ??? Neon loads and stores must be in use
> ??? Neon L1 caching must be disabled
> ??? Trustzone must be configured and in use
> ??? The secure memory address space and the non-secure memory address space both use the same
> physical addresses, either as an alias or the same memory location or for separate memory
> locations
> The issue is reported by ARM, erratum ID 468414, Category 2"
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> arch/arm/cpu/armv7/mx5/lowlevel_init.S | 9 +++++++++
> 1 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/cpu/armv7/mx5/lowlevel_init.S b/arch/arm/cpu/armv7/mx5/lowlevel_init.S
> index 683a7b5..c1a04db 100644
> --- a/arch/arm/cpu/armv7/mx5/lowlevel_init.S
> +++ b/arch/arm/cpu/armv7/mx5/lowlevel_init.S
> @@ -24,6 +24,13 @@
> #include <generated/asm-offsets.h>
> #include <linux/linkage.h>
>
> +.macro init_arm_erratum
> + /* ARM erratum ID #468414 */
> + mrc 15, 0, r1, c1, c0, 1
> + orr r1, r1, #(1 << 5) /* enable L1NEON bit */
> + mcr 15, 0, r1, c1, c0, 1
> +.endm
> +
> /*
> * L2CC Cache setup/invalidation/disable
> */
> @@ -338,6 +345,8 @@ ENTRY(lowlevel_init)
> str r1, [r0, #0x4]
> #endif
>
> + init_arm_erratum
> +
I have only a small question. It is not for me to put this into MX5
stuff, but because it is ARM related should we not put it into
arch/arm/cpu/armv7/start.S ?
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2012-05-09 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 20:56 [U-Boot] [PATCH] mx5: Add workaround for ARM erratum ID 468414 Fabio Estevam
2012-05-09 9:36 ` Stefano Babic [this message]
2012-10-17 16:28 ` Stefano Babic
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=4FAA3A9E.2090506@denx.de \
--to=sbabic@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.