linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: [PATCH 0/3] SRAM map series
Date: Sun,  8 Aug 2010 15:46:23 +0530	[thread overview]
Message-ID: <1281262583-27392-1-git-send-email-santosh.shilimkar@ti.com> (raw)

Currently we map 1 MB section while setting up SRAM on OMAPs.
The actual physcal OCM RAM available on OMAP SOCs is in order
of KBs. On the newer ARMs with speculation, this is dangerous and can
result in untraceable aborts.
On Davinci as well because of section limitation the SRAM is
marked as MT_DEVICE

First patch of this series addresses the section mapping limiaton and
now we can map such memories as page level granularity.

The series is generated against latest manline commit "2d530569730"
and boot tested on OMAP4430SDP, OMAP3430SDP platforms with 
omap_4430sdp_defconfig and multi-omap(omap3_defconfig) builds

Santosh Shilimkar (3):
  ARM: mmu: Setup MT_MEMORY and MT_MEMORY_NONACHED L1 entries
  omap1/2/3/4: map only available SRAM
  davinci: Map sram using MT_MEMORY_NONCACHED instead of MT_DEVICE

 arch/arm/mach-davinci/dm355.c  |    3 +--
 arch/arm/mach-davinci/dm365.c  |    3 +--
 arch/arm/mach-davinci/dm644x.c |    3 +--
 arch/arm/mach-davinci/dm646x.c |    3 +--
 arch/arm/mm/mmu.c              |   18 ++++++++++++++++--
 arch/arm/plat-omap/sram.c      |   25 +++++--------------------
 6 files changed, 25 insertions(+), 30 deletions(-)


             reply	other threads:[~2010-08-08 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-08 10:16 Santosh Shilimkar [this message]
2010-08-17  5:34 ` [PATCH 0/3] SRAM map series Shilimkar, Santosh

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=1281262583-27392-1-git-send-email-santosh.shilimkar@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@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;
as well as URLs for NNTP newsgroup(s).