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(-) -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
