From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: pxa: PXA270 D-Cache as ram
Date: Tue, 21 May 2013 21:24:36 +0200 [thread overview]
Message-ID: <201305212124.36467.marex@denx.de> (raw)
In-Reply-To: <1369163916.12900.36.camel@host5.omatika.ru>
Dear Sergey Yanovich,
> Dear Marek Vasut,
>
> On Tue, 2013-05-21 at 21:02 +0200, Marek Vasut wrote:
> > > The whole 256 kB of SRAM could be used for persistent storage with the
> > > patch. Without it, part of SRAM should be dedicated for U-Boot stack or
> > > be overwritten on boot.
> >
> > This won't hold on any PXA that uses SPL, like the vpac270 with OneNAND
> > SPL and PXA3xx (which is out of tree, none of your concern ;-) )
>
> I am no way trying to enforce D-Cache as RAM. The patch just provides an
> option for those who needs it.
I'd love to have a uniform way to do this cache thing, really ...
> > > You are right. After SDRAM is configured, it is enough to turn on data
> > > caching to receive its speed benefits.
> >
> > You must make sure anything that uses DMA won't crash.
>
> I wasn't sure why data cache is disabled in U-Boot for every board I saw
> configuration of. Thanks for pointing out.
>
> > But I don't understand
> > how locking cachelines as RAM and enabling dcache relate to each other in
> > this context.
>
> I meant D-Cache is several times faster than SDRAM, so it may be
> possible to get a bit faster, if stack remains on D-Cache even after
> SDRAM is configured.
Not really, enabling dcache altogether and marking DRAM region as cached would
be much better.
> Repeating my hedge, I don't see the full picture,
> yet. It may well be impossible (if U-Boot needs more than 32 kB of
> stack)
No way.
> or not worth the effort (if the gain is too small).
The larger gain would be from fixing the U-Boot drivers for PXA to work well
with DCache ;-) Then the speedup would really be plenty significant, this can be
well confirmed on many other ARM chips.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-05-21 19:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 22:06 [U-Boot] [PATCH] arm: pxa: PXA270 D-Cache as ram Sergey Yanovich
2013-05-21 10:39 ` Marek Vasut
2013-05-21 10:42 ` Sergey Yanovich
2013-05-21 10:54 ` Marek Vasut
2013-05-21 11:23 ` Sergey Yanovich
2013-05-21 11:38 ` Marek Vasut
2013-05-21 11:56 ` Sergey Yanovich
2013-05-21 15:00 ` Marek Vasut
2013-05-21 16:31 ` Sergey Yanovich
2013-05-21 19:02 ` Marek Vasut
2013-05-21 19:18 ` Sergey Yanovich
2013-05-21 19:24 ` Marek Vasut [this message]
2013-05-21 19:42 ` Sergey Yanovich
2013-05-21 20:07 ` Marek Vasut
2013-05-21 20:24 ` Sergey Yanovich
2013-05-21 21:38 ` Marek Vasut
2013-05-22 13:02 ` Sergey Yanovich
2013-05-22 13:04 ` Marek Vasut
2013-05-22 13:21 ` Sergey Yanovich
2013-05-22 13:54 ` Marek Vasut
2013-05-23 17:43 ` Mike Dunn
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=201305212124.36467.marex@denx.de \
--to=marex@denx.de \
--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