On Wed, Jul 11, 2012 at 4:20 PM, Joe Woodward <jw@xxxxxxxxxxxxxx> wrote: > -----Original Message----- > From: Kevin Hilman <khilman@xxxxxx> > To: "Joe Woodward" <jw@xxxxxxxxxxxxxx> > Cc: "linux-omap\@vger.kernel.org" <linux-omap@xxxxxxxxxxxxxxx> > Date: Tue, 10 Jul 2012 16:58:18 -0700 > Subject: Re: PM/RTC 3.5-rc5: System suspends fails when not built with RTC? > >> "Joe Woodward" <jw@xxxxxxxxxxxxxx> writes: >> >> > I've got 3.5-rc5 with the following patches applied to get system >> suspend working on OMAP3: >> > - fix the DSS: OMAPDSS: Use PM notifiers for system suspend >> > - fix the 32KHz clock: ARM: OMAP2+: hwmod code/clockdomain data: >> fix 32K sync timer >> > >> > This has been built with the omap2plus_defconfig. >> > >> > However, If I disable the RTC (i.e. >> CONFIG_RTC_CLASS/CONFIG_RTC_DRV_TWL4030) and rebuild then when >> suspending the device never wakes up. >> > >> > That is, I can't get any wakeups to happen (either through the >> console, or GPIO buttons) hence I'm assuming the kernel has crashed... >> > >> > Any ideas? >> > >> > As far as I know there is no dependency on the RTC in 3.4, and with >> the RTC compiled in I never see a problem on 3.5-rc5. >> >> There is definitely a bug in the EHCI driver in v3.5 that cause a hang >> in suspend, but the RTC connection is very strange. >> >> I was not able to reproduce this. >> >> Can you try the same with my current 'pm' branch[1]. I've got a >> handful >> of additional fixes there for various other problems where both MMC and >> EHCI are preventing sucessful suspend with the default >> omap2plus_defconfig. (note the EHCI fix is simply diabling it in the >> defconfig.) >> >> Kevin >> > > Hi Kevin, > > Thanks for looking in to this. > > I've taken a copy of the PM branch with tag "pm-20120710" and built with omap2plus_defconfig. > > But I get several warnings during boot, and suspend works - but almost nothing enters the target states: > > Warnings include: > [ 0.000000] clockdomain: mpu_clkdm: powerdomain ¬õ`À8ºsÀ does not exist > > [ 2.311004] omap_hsmmc omap_hsmmc.0: Failed to get debounce clk > [ 2.317382] omap_hsmmc omap_hsmmc.0: unable to obtain RX DMA engine channel 62 > [ 2.325256] omap_hsmmc omap_hsmmc.1: Failed to get debounce clk > [ 2.331512] omap_hsmmc omap_hsmmc.1: unable to obtain RX DMA engine channel 48 > Hi Joe, This warning should go away with CONFIG_DMA_OMAP, CONFIG_DMA_ENGINE enabled > [ 2.447784] platform omap_hsmmc.0: omap_device_late_idle: enabled but no driver. Idling > [ 2.456359] platform omap_hsmmc.1: omap_device_late_idle: enabled but no driver. Idling > -- 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
