From: Kevin Hilman <khilman@ti.com>
To: Joe Woodward <jw@terrafix.co.uk>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: PM/RTC 3.5-rc5: System suspends fails when not built with RTC?
Date: Tue, 10 Jul 2012 16:58:18 -0700 [thread overview]
Message-ID: <87zk77p3s5.fsf@ti.com> (raw)
In-Reply-To: <WC20120705150314.450045@terrafix.co.uk> (Joe Woodward's message of "Thu, 05 Jul 2012 16:03:14 +0100")
"Joe Woodward" <jw@terrafix.co.uk> 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
[1] git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git pm
next prev parent reply other threads:[~2012-07-10 23:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 15:03 PM/RTC 3.5-rc5: System suspends fails when not built with RTC? Joe Woodward
2012-07-10 23:58 ` Kevin Hilman [this message]
2012-07-11 10:50 ` Joe Woodward
2012-07-11 15:31 ` T Krishnamoorthy, Balaji
2012-07-11 17:07 ` Kevin Hilman
2012-07-11 17:51 ` Mark A. Greer
2012-07-11 18:38 ` Kevin Hilman
2012-07-11 18:48 ` Kevin Hilman
2012-07-11 20:52 ` Omar Ramirez Luna
2012-07-11 21:29 ` Kevin Hilman
2012-07-12 5:56 ` Shubhrajyoti
2012-07-13 6:34 ` Tony Lindgren
2012-07-16 17:18 ` Kevin Hilman
2012-07-12 8:15 Joe Woodward
2012-07-12 10:59 ` Paul Walmsley
2012-07-12 14:43 ` Joe Woodward
2012-07-12 19:35 ` Paul Walmsley
2012-07-13 10:57 ` Joe Woodward
2012-07-13 18:26 ` Paul Walmsley
2012-07-13 21:28 ` Mark A. Greer
2012-07-17 0:40 ` Mark A. Greer
2012-07-17 0:43 ` Paul Walmsley
2012-07-17 10:08 ` Joe Woodward
2012-07-17 19:28 ` Paul Walmsley
2012-07-18 2:20 ` Mark A. Greer
2012-07-18 10:06 ` Joe Woodward
2012-07-18 17:26 ` Mark A. Greer
2012-07-26 21:09 ` Juha Kuikka
2012-07-26 23:06 ` Mark A. Greer
2012-07-26 23:08 ` Mark A. Greer
2012-07-12 18:25 ` Kevin Hilman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zk77p3s5.fsf@ti.com \
--to=khilman@ti.com \
--cc=jw@terrafix.co.uk \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.