public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: PXA3xx internal SRAM
       [not found] ` <771cded01003211747n29be55a3p7608578ff1744f51@mail.gmail.com>
@ 2010-03-22  7:57   ` Daniel Mack
  0 siblings, 0 replies; only message in thread
From: Daniel Mack @ 2010-03-22  7:57 UTC (permalink / raw)
  To: Haojian Zhuang; +Cc: Eric Miao, linux-arm-kernel, linux-kernel

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


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-03-22  7:58 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20100321124739.GG30801@buzzloop.caiaq.de>
     [not found] ` <771cded01003211747n29be55a3p7608578ff1744f51@mail.gmail.com>
2010-03-22  7:57   ` PXA3xx internal SRAM Daniel Mack

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox