> -----Original Message----- > From: Jean Pihet [mailto:jean.pihet@xxxxxxxxxxxxxx] > Sent: Monday, November 22, 2010 5:01 PM > To: Rajendra Nayak > Cc: linux-omap@xxxxxxxxxxxxxxx; Jean Pihet-XID; Kevin Hilman > Subject: Re: [PATCH] OMAP3: disable idle early in the suspend sequence > > On Mon, Nov 22, 2010 at 11:53 AM, Rajendra Nayak <rnayak@xxxxxx> wrote: > >> -----Original Message----- > >> From: linux-omap-owner@xxxxxxxxxxxxxxx > > [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Jean Pihet > >> Sent: Monday, November 22, 2010 4:15 PM > >> To: linux-omap@xxxxxxxxxxxxxxx > >> Cc: Jean Pihet; Kevin Hilman > >> Subject: [PATCH] OMAP3: disable idle early in the suspend sequence > >> > >> Some bad interaction between the idle and the suspend paths has been > >> noticed: the idle code is called during the suspend enter and exit > >> sequences. This could cause corruption or lock-up of resources. > > > > Can you elaborate more on what kind of issues were seen? > > Trying to get the PRCM registers dump after a suspend/resume does not > show the correct registers values, cf. Kevin's patch at > http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap- > pm.git;a=commitdiff;h=9fc4891d4a21d2b644a463d62c77ef97da55f091. > > Digging a bit further I found out that the idle routine is called >50 > times while the suspend/resume sequence still is on-going. The root > cause is because disable_hlt is called from omap3_pm_prepare which > runs after omap3_pm_begin (and the same issue in the resume sequence). > This leaves a time window for idle to kick-in while the suspend > sequence is busy saving/restoring the system state. This is a > potential bug that just waits to show up soon or later, especially if > more code is added in the suspend prepare and finish functions. Ok. Thanks. Basically we had some similar issues on OMAP4. I am yet to root cause, but the initial hunch was there was a race between idle and suspend and I did pretty much the same change in pm44xx.c. That fixed the issue but only partially, so am still in the process of debugging it further to see what exactly is the issue. So was just curious to know what issues you ran into on OMAP3. Will update once I know whats happening on OMAP4. > > Does the changelog need an update? No, The changelog looks fine to me. Thanks, Rajendra > > Regards, > Jean -- 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
