On Mon, May 21, 2012 at 5:40 AM, Shilimkar, Santosh <santosh.shilimkar@xxxxxx> wrote: > >>> > Not sure what you mean wakeup issue on GP device. > > IIUC, the issue is: > Wakeup from device OFF, hardware releases the reset for both CPUs, > This is special case and applicable only for device OFF. The reason > CPU1 needs to be hold back, because the security SW is affined with > CPU0 which needs to be up and running for any of the ROM code APIs > to work. Like setting up SMP bit, AUX control etc. Without CPU0 booted, > CPU1 won't be able to execute those ROM functions and hence won't be > able to boot properly. > > I think the limitation is applicable to all OMAP4 devices as well as OMAP5 > devices. yes, the stagger of CPU1 behind CPU0 has a few factors: HS devices with an older PPA release has a bug where caches can be messed up and GP devices need slightly different WA. with the older PPA, we put CPU1 back to OFF when we detect that CPU0 is not ready for action you can find the details and documentation in the link below: http://git.omapzoom.org/?p=kernel/omap.git;a=blob;f=arch/arm/mach-omap2/sleep44xx.S;h=0c28def8f644e9803564bb66c8cfe8c580898978;hb=p-android-omap-3.0#l342 Regards, Nishanth Menon -- 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
