From: Fabian Cenedese <Cenedese@indel.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] P2020 SPL L2 clearing
Date: Mon, 07 Feb 2011 11:22:11 +0100 [thread overview]
Message-ID: <5.2.0.9.1.20110207111943.03e4a320@localhost> (raw)
In-Reply-To: <5.2.0.9.1.20110202172529.04ab5e68@localhost>
At 14:17 03.02.2011 +0100, Fabian Cenedese wrote:
>Hi
>
>I'm creating a SPL u-boot image for our board. In the file
>arch/powerpc/cpu/mpc85xx/cpu_init_nand.c is the setup for
>the L2 cache as SRAM. In the end is a loop that fills the
>cache with 0 (512KB in this case).
>
> /* Initialize L2 SRAM to zero */
> l2srbar = (char *)CONFIG_SYS_INIT_L2_ADDR;
> for (i = 0; i < CONFIG_SYS_L2_SIZE; i++)
> l2srbar[i] = 0;
>
>Two questions for this:
>
>1. Why is the access byte-wise and not dword-wise? This
>is only for mpc85xx and I think they all can access the cache
>with 32bits instead of just 8. That would speed up by factor 4
>(confirmed in my tests with P2020).
>
>2. Why does the cache to be cleared at all? L2-SRAM is usually
>just used to copy in the second part of the u-boot image, so
>the 0s will be overwritten again anyway.
>
>I came to this loop because the board takes an awful long
>time to boot up. I'm measuring now cpu ticks until board_init_r
>(in the first part loader before the u-boot image gets loaded).
>With this loop it takes about 4 seconds, without just 50 ms.
>How come the L2 access is so slow? I already increased
>the lb clock but that only helps "outside". Even if this loop
>didn't need any time I'd still have the questions above.
I just wanted to ask again if somebody has any insight
on this. Maybe Kumar?
Thanks
bye Fabi
next prev parent reply other threads:[~2011-02-07 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 13:17 [U-Boot] P2020 SPL L2 clearing Fabian Cenedese
2011-02-07 10:22 ` Fabian Cenedese [this message]
2011-02-08 16:55 ` Kumar Gala
2011-02-09 8:06 ` Fabian Cenedese
2011-02-09 16:18 ` Kumar Gala
2011-02-11 14:34 ` Fabian Cenedese
2011-02-12 17:44 ` Kumar Gala
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=5.2.0.9.1.20110207111943.03e4a320@localhost \
--to=cenedese@indel.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox