From: joshc@ni.com (Josh Cartwright)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: zynq: address silent L2 cache corruption
Date: Tue, 2 Feb 2016 20:30:47 -0600 [thread overview]
Message-ID: <cover.1454465714.git.joshc@ni.com> (raw)
The Zynq has a bug where the L2 cache will return invalid data in some
circumstances unless the L2C_RAM register is set to 0x20202 before the first
enabling of the L2 cache.
The Xilinx-recommended solution to this problem is to ensure that early one of
the earlier bootstages correctly initialize L2C_RAM, however, this issue wasn't
discovered and fixed until after their EDK/SDK 14.4 release. For systems built
prior to that, and which lack field-upgradable bootloaders, this issue still
exists and silent data corruption can be seen in the wild.
Fix these systems by ensuring L2C_RAM is properly initialized at the
earliest convenient moment prior to the L2 being brought up, which is
when the SLCR is first mapped.
Unfortunately, there isn't much public documentation on exactly what the
L2C_RAM register is for, or how it is used, only that software is responsible
for initializing it to the proper value prior to bringing up L2.
You can find more information about this bug in AR#54190[1].
1: http://www.xilinx.com/support/answers/54190.html
Josh Cartwright (2):
ARM: zynq: initialize slcr mapping earlier
ARM: zynq: address L2 cache data corruption
arch/arm/mach-zynq/common.c | 3 +--
arch/arm/mach-zynq/slcr.c | 4 ++++
2 files changed, 5 insertions(+), 2 deletions(-)
--
2.7.0
next reply other threads:[~2016-02-03 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 2:30 Josh Cartwright [this message]
2016-02-03 2:30 ` [PATCH 1/2] ARM: zynq: initialize slcr mapping earlier Josh Cartwright
2016-02-03 2:30 ` [PATCH 2/2] ARM: zynq: address L2 cache data corruption Josh Cartwright
2016-02-09 9:19 ` [PATCH 0/2] ARM: zynq: address silent L2 cache corruption Michal Simek
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=cover.1454465714.git.joshc@ni.com \
--to=joshc@ni.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).