From: Daniel Mack <daniel@caiaq.de>
To: Haojian Zhuang <haojian.zhuang@gmail.com>
Cc: Eric Miao <eric.y.miao@gmail.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: PXA3xx internal SRAM
Date: Mon, 22 Mar 2010 08:57:39 +0100 [thread overview]
Message-ID: <20100322075739.GI30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <771cded01003211747n29be55a3p7608578ff1744f51@mail.gmail.com>
On Sun, Mar 21, 2010 at 08:47:22PM -0400, Haojian Zhuang wrote:
> On Sun, Mar 21, 2010 at 8:47 AM, Daniel Mack <daniel@caiaq.de> wrote:
> > The pxa3xx series features a comparatively big and fast internal SRAM of
> > 256KB which is currently unused by the Linux kernel except for a 4-byte
> > return vector from suspend.
> >
> > I wonder what this could be used for. Is there any kind of cache that
> > would be worth putting there to speed up things for example?
> > And could the uncompressor probably benfit from that?
> >
> > Daniel
>
> The size of internal SRAM isn't always 256KB. It could be 128KB, 256KB
> or 702KB. In marvell BSP, there's a memory management driver (aka IMM)
> to handle internal SRAM. So driver or user application could make use
> of it. And one part of internal SRAM is reserved for low power idle
> mode. But both of these two features aren't pushed into community yet.
Ok. I was more thinking about any kernel specific kind of cache that has
a fix size of 128kb or 256kb and which is consulted regularily. But I
don't know which kind of cache that could be.
As that's not neccessarily ARM-related, I copied LKML. Maybe anyone has
an idea.
Thanks,
Daniel
parent reply other threads:[~2010-03-22 7:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <771cded01003211747n29be55a3p7608578ff1744f51@mail.gmail.com>]
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=20100322075739.GI30801@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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