From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] arc: significant cache rework
Date: Wed, 1 Jul 2015 14:20:44 +0000 [thread overview]
Message-ID: <1435760444.4689.51.camel@synopsys.com> (raw)
In-Reply-To: <1435760131-369-1-git-send-email-abrodkin@synopsys.com>
On Wed, 2015-07-01 at 17:15 +0300, Alexey Brodkin wrote:
> From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
>
> [1] Align cache management functions to those in Linux kernel. I.e.:
> a) Use the same functions for all cache ops (D$ Inv/Flush)
> b) Split cache ops in 3 sub-functions: "before", "lineloop" and
> "after". That way we may re-use "before" and "after" functions for
> region and full cache ops.
>
> [2] Implement full-functional L2 (SLC) management. Before SLC was
> simply disabled early on boot. If SLC exists corresponding ops are
> run on cache
> flush/invalidate.
>
> [3] Disable/enable corresponding caches early on boot. So if U-Boot
> is
> configured to use caches they will be used at all times (this is
> useful
> in particular for speed-up of relocation).
>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> ---
> Compared to v1:
> * Remove explicit selection of L2CACHE on/off in Kconfig, check this
> in runtime
> and use L2 ops only when L2 is detected.
> This allows run the same executable on HW with and without L2
> cache.
> ---
> arch/arc/include/asm/arcregs.h | 5 +-
> arch/arc/include/asm/cache.h | 7 +-
> arch/arc/lib/cache.c | 375 ++++++++++++++++++++++++++++---
> ----------
> arch/arc/lib/cpu.c | 2 +
> arch/arc/lib/init_helpers.c | 10 +-
> arch/arc/lib/start.S | 46 ++++-
> 6 files changed, 300 insertions(+), 145 deletions(-)
Applied, thanks.
-Alexey
prev parent reply other threads:[~2015-07-01 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 14:15 [U-Boot] [PATCH v2] arc: significant cache rework Alexey Brodkin
2015-07-01 14:20 ` Alexey Brodkin [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=1435760444.4689.51.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--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