From: Stefan Roese <sr@denx.de>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/2] [POWERPC] Add PPC4xx L2-cache support (440GX & 460EX/GT)
Date: Thu, 20 Mar 2008 08:12:08 +0100 [thread overview]
Message-ID: <200803200812.08282.sr@denx.de> (raw)
In-Reply-To: <1205996092.26869.420.camel@pasglop>
On Thursday 20 March 2008, Benjamin Herrenschmidt wrote:
> On Tue, 2008-03-18 at 14:36 +0100, Stefan Roese wrote:
> > This patch adds support for the 256k L2 cache found on some IBM/AMCC
> > 4xx PPC's. It introduces a common 4xx SoC file (sysdev/ppc4xx_soc.c)
> > which currently "only" adds the L2 cache init code. Other common 4xx
> > stuff can be added later here.
> >
> > The L2 cache handling code is just a copy of Eugene's code in arch/ppc
> > with small modifications.
> >
> > Tested on AMCC Taishan 440GX and Canyonlands 460EX.
> >
> > Signed-off-by: Stefan Roese <sr@denx.de>
>
> It's my understanding that on some 44x platforms, the l2 needs to be
> explicitely invalidated on DMAs.
Correct.
> Do we know more about that ? I think it
> depends on something like the number of masters on the PLB4 or so. I
> don't remember the details.
The L2 cache on the 440GX is cache coherent (via snooping). On the
440SP/440SPe the L2 cache is partially coherent. The LL (Low Latency) PLB
segment is coherent and the HB (High Bandwidth) PLB segment is unfortunately
not. Here an except from the 440SPe users manual:
"
Cache coherency is limited to the Low Latency (LL) PLB bus and is managed by a
hardware snoop mechanism or software (software that is similar to the
existing CPU L1 cache)
"
So we will need to add something to handle the L2 cache on those platforms
correctly. Not needed on 440GX though.
As for 460EX/GT this is currently not clear yet. I'm working on it with AMCC
right now.
Best regards,
Stefan
prev parent reply other threads:[~2008-03-20 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 13:36 [PATCH 1/2] [POWERPC] Add PPC4xx L2-cache support (440GX & 460EX/GT) Stefan Roese
2008-03-19 23:27 ` Stephen Rothwell
2008-03-20 6:35 ` Stefan Roese
2008-03-20 6:54 ` Benjamin Herrenschmidt
2008-03-20 7:12 ` Stefan Roese [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=200803200812.08282.sr@denx.de \
--to=sr@denx.de \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).