On 6 December 2010 17:35, Dave Martin <[email protected]> wrote: > * Explicitly build a few parts of sleep34xx.S as ARM. > > * lock_scratchpad_sem is kept as ARM because of the need to > synchronise with hardware (?) using the SWP instruction. > > * save_secure_ram_context and omap34xx_cpu_suspend are built > as ARM in case the Secure World firmware expects to decode > the comment field from the SMC (aka smi) instructions. > > This can be undone later if the firmware is confirmed as > able to decode the Thumb SMC encoding (or ignores the > comment field). > > * es3_sdrc_fix should presumably only be called from the > low-level wakeup code. To minimise the diff, switched this > to ARM and demoted it to be a local symbol, since I believe > it shouldn't be called from outside anyway.
I haven't checked the code but does this always work? The kernel isn't built with interworking enabled, so it's either ARM or Thumb-2. -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
