From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/4xx: Add L2 cache node to AMCC Canyonlands dts file
Date: Fri, 5 Dec 2008 06:08:35 -0500 [thread overview]
Message-ID: <20081205060835.46c6df7a@zod.rchland.ibm.com> (raw)
In-Reply-To: <1228457332-523-1-git-send-email-sr@denx.de>
On Fri, 5 Dec 2008 07:08:52 +0100
Stefan Roese <sr@denx.de> wrote:
> With this patch the L2 cache is enabled on Canyonlands to increase the
> overall performance. There is a known cache coherency issue with the L2
> cache, but this is related to the high bandwidth (HB) PLB segment where
> the memory address is 0x8.xxxx.xxxx (low bandwidth PLB segment is mapped
> to 0x0.xxxx.xxxx). Since this HB address is currently unused it is safe
> to enable the L2 cache.
>
> Signed-off-by: Stefan Roese <sr@denx.de>
> ---
> arch/powerpc/boot/dts/canyonlands.dts | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/arch/powerpc/boot/dts/canyonlands.dts b/arch/powerpc/boot/dts/canyonlands.dts
> index 79fe412..0d77482 100644
> --- a/arch/powerpc/boot/dts/canyonlands.dts
> +++ b/arch/powerpc/boot/dts/canyonlands.dts
> @@ -104,6 +104,16 @@
> dcr-reg = <0x00c 0x002>;
> };
>
> + L2C0: l2c {
> + compatible = "ibm,l2-cache-460ex", "ibm,l2-cache";
> + dcr-reg = <0x020 0x008 /* Internal SRAM DCR's */
> + 0x030 0x008>; /* L2 cache DCR's */
> + cache-line-size = <32>; /* 32 bytes */
> + cache-size = <262144>; /* L2, 256K */
> + interrupt-parent = <&UIC1>;
> + interrupts = <11 1>;
> + };
Shouldn't there also be a next-level-cache property added to the cpu
node that references this?
josh
next prev parent reply other threads:[~2008-12-05 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 6:08 [PATCH] powerpc/4xx: Add L2 cache node to AMCC Canyonlands dts file Stefan Roese
2008-12-05 11:08 ` Josh Boyer [this message]
2008-12-05 11:11 ` Benjamin Herrenschmidt
2008-12-05 11:17 ` Stefan Roese
2008-12-05 21:04 ` Nathan Lynch
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=20081205060835.46c6df7a@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@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;
as well as URLs for NNTP newsgroup(s).