On Tue, Aug 28, 2012 at 04:38:24PM -0700, Shilimkar, Santosh wrote:

On Tue, Aug 28, 2012 at 4:09 PM, Aaro Koskinen [off-list ref] wrote:

quoted

On Tue, Aug 28, 2012 at 07:19:38AM -0700, Shilimkar, Santosh wrote:

quoted

Or the PPA has resized the secure area of 16K. As you have seen the issue
on one OMAP3 device, it makes sense to takeout that 16K from the public
SRAM map.

Can you send the patch with fixed base address fir PUB SRAM ?

Maybe I'm missing something, but I tried the following and now something
else got broken:

        save_secure_sram() returns 0000ff02

Damn. Looks like, you are running short of memory now for sram_push stuff.

No, it's not that, because the below version works and that leaves as
little memory for the sram_push code:

diff --git a/arch/arm/plat-omap/sram.c b/arch/arm/plat-omap/sram.c
index 766181c..a91e7ad 100644
--- a/arch/arm/plat-omap/sram.c
+++ b/arch/arm/plat-omap/sram.c

@@ -47,7 +47,7 @@
 #define OMAP5_SRAM_PA		0x40300000
 
 #if defined(CONFIG_ARCH_OMAP2PLUS)
-#define SRAM_BOOTLOADER_SZ	0x00
+#define SRAM_BOOTLOADER_SZ	(cpu_is_omap34xx() ? SZ_16K : 0)
 #else
 #define SRAM_BOOTLOADER_SZ	0x80
 #endif

A.