Hi Tomasz, On Sat, Dec 21, 2013 at 3:23 AM, Tomasz Figa <tomasz.figa@xxxxxxxxx> wrote: > On Friday 20 of December 2013 13:37:36 Olof Johansson wrote: >> On Fri, Dec 20, 2013 at 1:19 PM, Tomasz Figa <tomasz.figa@xxxxxxxxx> wrote: >> > Hi, >> > >> > On Friday 20 of December 2013 15:56:38 sunil joshi wrote: >> >> Hi Abhilash, >> >> I saw another patch in chrome tree ..by Andrew Bresticker >> >> which may be relevant here .. >> >> >> >> Just wondering if you missed adding this ? or this is not needed ? >> >> You did not face any issue in getting core to suspend ? >> >> >> >> ------------------------------------------------------------------------------------------ >> >> commit 95402d816b9f1a05ce633f7ff64b4c939c142482 >> >> Author: Andrew Bresticker <abrestic@xxxxxxxxxxxx> >> >> Date: Mon Jul 15 13:14:36 2013 -0700 >> >> >> >> arm: exynos: disable all interrupts on Exynos5420 before suspend >> >> >> >> Disable all interrupts from the GIC before entering suspend on >> >> Exynos5420 as is done on Exynos5250. If interrupts are enabled, we >> >> may receive an interrupt after entering WFI but before the PMU has >> >> suspended the system, causing suspend to fail. >> >> >> >> BUG=chrome-os-partner:20523 >> >> TEST=Run suspend_stress_test on Pit and observe that entering suspend >> >> no longer occasionally fails with the "Failed to suspend the system" >> >> error in exynos_cpu_suspend(). >> > >> > A question about this for Chromium and LSI guys: >> > >> > If you find out that there is already a pending interrupt before you enter >> > the sleep mode, isn't it more reasonable to cancel the process ASAP and >> > handle the event instead of entering the sleep just to leave it? >> > >> > I believe this should be both more efficient with respect to power usage >> > and latency, because sleep-wakeup transition takes time and power. >> > >> > Do you have any reason to think the opposite? >> >> If it's expected to be a rare or very rare event, it's not a given >> that the added complexity of dealing with the aborted suspend that >> late is worth it. > > I think that the code to support this is already in place, just printing > an unfortunate message about "suspend failures". It doesn't add any > significant complexity too. > > I'm not sure about the frequency of such events, though, and any real > effect of this or the other behavior in such case and so there is my > question about this. Adding to what Doug already mentioned in the thread, in the cases where we saw cpu_do_idle fail we noticed the following: 1) No wake-up source as having woken up the system (by checking the WAKEUP_STAT) 2) On checking all the EINT Pend registers the values indicated no pending interrupts. The UM says that the PMU may fail to go to suspend when there are pending interrupt events. The patch assumed that we have a non-wakeup interrupt pending causing "wfi" to fail, especially as we saw the failure more often with no_console_suspend. > > Best regards, > Tomasz Abhilash > -- 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
 |