* [PATCH 0/3] SRAM map series
@ 2010-08-08 10:16 Santosh Shilimkar
2010-08-17 5:34 ` Shilimkar, Santosh
0 siblings, 1 reply; 2+ messages in thread
From: Santosh Shilimkar @ 2010-08-08 10:16 UTC (permalink / raw)
To: linux-omap; +Cc: linux-arm-kernel, Santosh Shilimkar
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(-)
^ permalink raw reply [flat|nested] 2+ messages in thread
* RE: [PATCH 0/3] SRAM map series
2010-08-08 10:16 [PATCH 0/3] SRAM map series Santosh Shilimkar
@ 2010-08-17 5:34 ` Shilimkar, Santosh
0 siblings, 0 replies; 2+ messages in thread
From: Shilimkar, Santosh @ 2010-08-17 5:34 UTC (permalink / raw)
To: Tony Lindgren, khilman@deeprootsystems.com
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Tony/Kevin,
> -----Original Message-----
> From: Shilimkar, Santosh
> Sent: Sunday, August 08, 2010 3:46 PM
> To: linux-omap@vger.kernel.org
> Cc: linux-arm-kernel@lists.infradead.org; Shilimkar, Santosh
> Subject: [PATCH 0/3] SRAM map series
>
> 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
>
Can you please have a look at second and third patch?
First patch is reviewed by Russell already
> 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(-)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-08-17 5:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-08-08 10:16 [PATCH 0/3] SRAM map series Santosh Shilimkar
2010-08-17 5:34 ` Shilimkar, Santosh
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).