> -----Original Message----- > From: Shreyas Mahajan [mailto:mahajan.shreyas@xxxxxxxxx] > Sent: Tuesday, February 03, 2009 11:44 AM > To: Premi, Sanjeev; linux-omap@xxxxxxxxxxxxxxx > Subject: Re: Omap3430 does not resume after suspend > > On Fri, Jan 30, 2009 at 7:32 PM, Premi, Sanjeev <premi@xxxxxx> wrote: > > > > > -----Original Message----- > > > From: linux-omap-owner@xxxxxxxxxxxxxxx > > > [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Shreyas > > > Mahajan > > > Sent: Friday, January 30, 2009 2:54 PM > > > To: linux-omap@xxxxxxxxxxxxxxx > > > Subject: Omap3430 does not resume after suspend > > > > > > Hello, > > > I am a newbie with omap3430. As a part of my project, I > > > suspended my board with 'echo mem > /sys/power/state'.The suspend > > > happens correctly, without giving any failure message. > But, when I > > > tried it to resume, it is not resuming.I tried to find > some reasons > > > for this, and got the patches for unmasking keyboard > interrupt while > > > suspending. But, all patches are for omap2 and omap1 board > > > architecture. > > [sp] Are you following updates in Kevin Hilman's pm branch? > > With lastest updates you shouldn't see this problem on a > minimal config. > > > > Would be good to start from here and add drivers selectively. > > > > > Are there any patches to do this thing in omap3430? > > > > [sp] omap2 applies to OMAP3430 as well. > > > > > > > > Thanks, > > > -- > > > 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 > > > > > > > > Thanks for reply. > I went through the Kevin Hilman's PM branch and found the > same problem posted by you (@Sanjeev), > > 'Hangs on a echo mem > /sys/power/state > > Goes into suspend, but cannot recover' > > So, can you please tell me if this problem is solved? > [sp] Have not been able to follow-up in the latest tree for last couple of days, but with minimal driver configuration; this problem is solved. I am in process of finding the 'offending' driver.-- 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
