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 13:38:51 +0200 [thread overview]
Message-ID: <201305211338.52145.marex@denx.de> (raw)
In-Reply-To: <1369135414.12900.3.camel@host5.omatika.ru>
Dear Sergey Yanovich,
> Dear Marek Vasut,
>
> On Tue, 2013-05-21 at 12:54 +0200, Marek Vasut wrote:
> > SRAM is just the in-CPU bit of fast RAM. What do you mean by
> > "battery-backup" ?
>
> Yes, you are right. It is 'for high speed code or data storage preserved
> during low-power states' using a quote from PXA270 EMTS (top of page 1).
> Battery-backup is optional. I mixed PXA270 and LP-8x4x specs.
Yes, it's just an in-CPU RAM.
> > > It can be used as a ultra-fast persistent
> > > storage in OS. Wasting a quater of it just to boot the system isn't the
> > > best choice.
> >
> > The SRAM is used for stack in U-Boot until you leave board_init_f, then
> > the stack is relocated to DRAM. The OS can use SRAM as needed, U-Boot is
> > no longer operational once you load subsequent OS. What's the problem?
>
> Anyway, SRAM preserves its state when power is off. Poweroff time could
> be in years with a backup battery. In addition, D-Cache is an order of
> magnitude faster than SRAM (approx. 9 times) for both reads and writes.
Is there any measurable difference between using DCache and SRAM? Do you have
any evidence that a speedup happens?
Still, the SRAM/DCache is only used until you leave board_init_f(), then it's
all DRAM.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-05-21 11:38 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 [this message]
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
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=201305211338.52145.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