On 06/29/2013 12:47 AM, Tomasz Figa wrote: > On Friday 28 of June 2013 23:47:49 Daniel Lezcano wrote: >> On 06/28/2013 06:27 PM, Bartlomiej Zolnierkiewicz wrote: >>> On Friday, June 28, 2013 01:20:09 PM Daniel Lezcano wrote: >>>> On 06/28/2013 12:11 PM, Tomasz Figa wrote: >>>>> Hi Daniel, >>>>> >>>>> I've been fighting with this whole AFTR state as well, before >>>>> Bartlomiej. Let me share my thoughts on this. >> >> [ ... ] >> >>>>> If you don't unplug all the CPUs >0 the state is obviously never >>>>> reached. Otherwise the whole system hangs after it tries to enter >>>>> this mode without any reaction for external events, other than >>>>> reset. >>>> >>>> Need investigation. >>>> >>>> What is the exynos board version where that occurs ? >>> >>> Could you please tell me what exactly do you mean by that? >>> >>> I already wrote that we can reproduce the problem on EXYNOS4210 rev0 >>> and rev1.1 (we don't have rev1.0). Tomek has also reproduced the >>> problem on some later SoCs (I hope that he can give you exact >>> revisions). >>> >>> In our testing we didn't encounter the board on which the problem >>> doesn't occur. Our current working theory is that the problem may be >>> u-boot (or first stage bootloader) related. >> >> Ok, the status for what I know: >> >> Origen Exynos4210, board ver A: works for me >> Arndale Exynos5250: works for me but only if u-boot does not enable the >> hypervisor mode. >> Chromebook Exynos5250: works for me >> >> I found the following drivers: >> >> https://github.com/AndreiLux/Perseus-UNIVERSAL5410/blob/samsung/arch/arm >> /mach-exynos/cpuidle.c >> >> https://github.com/CyanogenMod/hardkernel-kernel-4412/blob/cm-10.1/arch/ >> arm/mach-exynos/cpuidle-exynos4.c >> >> Sounds like the num cpus > 1 is still there. > > As far as I know (and I can read from the documentation), AFTR is a state > in which program execution context (e.g. PC, CPU registers, etc.) is lost. > This is like sleep mode, but with much more state saved (all the > peripherals and L2 cache), which lets you resume much faster. > > Based on that, the execution flow is as following: > - kernel stops all secondary cores, > - kernel configures PMU to enter AFTR mode, > - WFI is executed on boot CPU, which lets PMU enter the requested low > power mode, > - the system stays with all CPU cores powered off until a wake-up event > happens, > - a wake-up event causes a wake-up reset of the boot CPU, which resumes > operation from reset vector (usually IROM), > - here exactly the same procedure is used as on wake-up from sleep mode, > with the exception that some assumptions can be made about kept state, > like BL1 being still in IRAM/SYSRAM, without the need to reload it from > boot device, > - after going through all the boot code, it finally jumps to the resume > handler saved by kernel in one of those INFORM registers or somewhere in > SYSRAM, > - resume handler reinitializes boot CPU, restores things like MMU, > coprocessors, etc. and finally boots secondary cores again, > - the system is operating normally again. > > This is simplified a lot, with all things happened internally in PMU and > boot code skipped, but should give the general picture. See all the > analogies to normal sleep mode, which (IMHO) makes it understandable that > this mode can't be entered with more than one core active. > > However, with something like coupled cpuidle, when possible, this mode can > be entered by powering down remaining cores automatically, so this is not > a problem with this mode itself, but rather with current approach of > entering it. Are you saying only CPU0 can program the PMU to enter the AFTR mode ? And only CPU0 can be woken up ? Is it possible to have CPU0 to enter the AFTR idle state (without switching to this mode), save its context and go to WFI. And then when CPU1 goes to this state also, it saves its context and set the PMU to enter the AFTR mode ? -- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |