From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 07/10] ARM: mvebu: implement Armada 375 coherency workaround
Date: Thu, 6 Mar 2014 22:18:21 +0100 [thread overview]
Message-ID: <20140306221821.771a0d12@skate> (raw)
In-Reply-To: <20140306183656.GE1872@titan.lakedaemon.net>
Dear Jason Cooper,
On Thu, 6 Mar 2014 13:36:56 -0500, Jason Cooper wrote:
> On Thu, Mar 06, 2014 at 05:46:32PM +0100, Thomas Petazzoni wrote:
> > The early revisions of Armada 375 SOCs (Z1 stepping) have a bug in the
>
> Do we have a way to determine that we are on a Z1 at runtime? It seems
> like we're consuming an XOR engine unconditionally. I presume that
> Marvell is going to fix this with the next stepping?
Yes, we believe there will be a way to differentiate the Z1 stepping
for the later steppings, using the mvebu-soc-id. However, since those
later steppings are not available yet, we haven't been able to test
this. Our plan is that as soon as we have newer steppings, we will
improve this code to only apply the XOR workaround on the steppings for
which it is needed. It is not clear at this point which stepping
exactly will fix the problem, so we've written the code with the
information that we have today.
Thanks for the feedback!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-06 21:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 16:46 [PATCH 00/10] ARM: mvebu: Hardware coherency support for Armada 375 and 38x Thomas Petazzoni
2014-03-06 16:46 ` [PATCH 01/10] ARM: mvebu: prepare coherency code to support more SOCs Thomas Petazzoni
2014-03-06 16:46 ` [PATCH 02/10] ARM: mvebu: add a coherency_available() call Thomas Petazzoni
2014-03-06 16:46 ` [PATCH 03/10] bus: mvebu: pass the coherency availability information at init time Thomas Petazzoni
2014-03-06 16:46 ` [PATCH 04/10] ARM: mvebu: ARM: mvebu: use of_find_matching_node_and_match() in coherency.c Thomas Petazzoni
2014-03-06 16:46 ` [PATCH 05/10] ARM: mvebu: enable the ARM SCU on Armada 375 and Armada 38x Thomas Petazzoni
2014-03-06 16:46 ` [PATCH 06/10] ARM: mvebu: add Armada 375 support to the coherency code Thomas Petazzoni
2014-03-06 16:46 ` [PATCH 07/10] ARM: mvebu: implement Armada 375 coherency workaround Thomas Petazzoni
2014-03-06 18:36 ` Jason Cooper
2014-03-06 21:18 ` Thomas Petazzoni [this message]
2014-03-06 16:46 ` [PATCH 08/10] ARM: mvebu: add Armada 38x support to the coherency code Thomas Petazzoni
2014-03-06 16:46 ` [PATCH 09/10] ARM: mvebu: enable the coherency fabric on Armada 375 Thomas Petazzoni
2014-03-06 16:46 ` [PATCH 10/10] ARM: mvebu: enable the coherency fabric on Armada 38x Thomas Petazzoni
2014-03-24 15:06 ` [PATCH 00/10] ARM: mvebu: Hardware coherency support for Armada 375 and 38x Thomas Petazzoni
2014-03-25 9:32 ` Andrew Lunn
2014-03-25 10:36 ` Thomas Petazzoni
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=20140306221821.771a0d12@skate \
--to=thomas.petazzoni@free-electrons.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).