linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: PXA3xx internal SRAM
Date: Sun, 21 Mar 2010 20:47:22 -0400	[thread overview]
Message-ID: <771cded01003211747n29be55a3p7608578ff1744f51@mail.gmail.com> (raw)
In-Reply-To: <20100321124739.GG30801@buzzloop.caiaq.de>

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
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>

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.

Thanks
Haojian

  reply	other threads:[~2010-03-22  0:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-21 12:47 PXA3xx internal SRAM Daniel Mack
2010-03-22  0:47 ` Haojian Zhuang [this message]
2010-03-22  7:57   ` Daniel Mack
2010-03-22 21:09 ` Linus Walleij
2010-03-25 12:58   ` Haojian Zhuang
2010-03-25 15:47     ` Linus Walleij
2010-03-26  2:55       ` Haojian Zhuang

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=771cded01003211747n29be55a3p7608578ff1744f51@mail.gmail.com \
    --to=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).