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: Suspend broken on 3.3?
Date: Thu, 22 Mar 2012 10:33:56 -0700 [thread overview]
Message-ID: <87r4wka6bf.fsf@ti.com> (raw)
In-Reply-To: <WC20120322110946.6413AA@terrafix.co.uk> (Joe Woodward's message of "Thu, 22 Mar 2012 11:09:46 +0000")
"Joe Woodward" <jw@terrafix.co.uk> writes:
> Is system suspend broken on stock 3.3?
I hope not. :)
It *should* work, I'm using it regularily here, and "it works for me"
(I'm sure that's just what you want to hear.) :)
> I have a working stock 3.2 (with patches to fix runtime_pm for DSS2), and system suspend works just fine!
>
> This is running on a variety of GUMSTIX boards (both OMAP3530 and AM3703-based).
I currently only have a 3530-based Gumstix Overo (although a
AM3xxx-based one is on the way, thanks Gumstix!), but it's working fine
for me on my Overo.
Stock v3.3 won't boot on Overo because of the smsc911x regulator issues
recently discusssed, so if you're using Overo, you also need the patch
in Tony's fix-smsc911x-regulator branch.
After that, suspend/resume is working fine for me using
omap2plus_defconfig. I tried both with initramfs and with MMC rootfs.
Can you try without your board file changes, using vanilla v3.3 +
smsc911x fix above and using omap2plus_defconfig?
Also, please share the kernel command-line you're using.
Thanks,
Kevin
next prev parent reply other threads:[~2012-03-22 17:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 11:09 Suspend broken on 3.3? Joe Woodward
2012-03-22 17:33 ` Kevin Hilman [this message]
2012-03-26 13:41 ` Joe Woodward
2012-03-27 0:34 ` Kevin Hilman
2012-03-27 13:53 ` Raja, Govindraj
2012-03-27 21:37 ` Kevin Hilman
2012-03-28 10:59 ` Raja, Govindraj
2012-03-28 15:38 ` Joe Woodward
2012-03-28 17:46 ` Kevin Hilman
2012-03-29 8:35 ` Joe Woodward
2012-03-29 9:14 ` Shubhrajyoti Datta
2012-03-29 9:46 ` Joe Woodward
2012-03-29 10:26 ` Paul Walmsley
2012-03-29 11:27 ` Joe Woodward
2012-03-29 11:40 ` Joe Woodward
2012-03-29 14:29 ` Raja, Govindraj
2012-03-30 7:53 ` Joe Woodward
2012-03-30 8:46 ` Raja, Govindraj
2012-03-30 9:26 ` Joe Woodward
2012-03-30 10:15 ` Raja, Govindraj
2012-03-30 11:04 ` Joe Woodward
2012-03-30 12:24 ` Raja, Govindraj
2012-04-02 10:43 ` Raja, Govindraj
2012-04-02 12:37 ` Joe Woodward
2012-04-03 6:56 ` Govindraj
2012-04-04 14:56 ` Paul Walmsley
2012-04-04 16:13 ` Raja, Govindraj
2012-04-06 0:29 ` Paul Walmsley
2012-04-06 14:21 ` Kevin Hilman
2012-04-09 11:27 ` Raja, Govindraj
2012-04-09 14:27 ` Kevin Hilman
2012-04-09 16:01 ` Paul Walmsley
2012-04-09 17:10 ` Kevin Hilman
2012-04-10 9:26 ` Raja, Govindraj
2012-04-10 18:03 ` Kevin Hilman
2012-04-11 13:13 ` Raja, Govindraj
2012-04-11 19:34 ` Paul Walmsley
2012-04-12 11:51 ` Raja, Govindraj
2012-03-27 14:39 ` Joe Woodward
2012-03-27 21:28 ` 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=87r4wka6bf.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.