From: Tero Kristo <t-kristo@ti.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
loml <linux-omap@vger.kernel.org>,
"Hilman, Kevin" <khilman@ti.com>
Subject: Re: suspend broken on 3.5-rc1?
Date: Fri, 8 Jun 2012 16:05:32 +0300 [thread overview]
Message-ID: <1339160732.2091.47.camel@sokoban> (raw)
In-Reply-To: <4FD1EF25.3060906@ti.com>
On Fri, 2012-06-08 at 17:55 +0530, Rajendra Nayak wrote:
> On Friday 08 June 2012 04:26 PM, Tony Lindgren wrote:
> > * Rajendra Nayak<rnayak@ti.com> [120608 03:40]:
> >> Hi,
> >>
> >> I don;t seem to be able to get suspend to work on 3.5-rc1 on
> >> my 4430 panda. I am not sure if its UART wakeups that are
> >> an issue or suspend itself is broken.
> >> Is there anything more than setting
> >> '/sys/devices/platform/omap_uart.2/tty/ttyO2/power/wakeup'
> >> to 'enabled' that I need to do to get UART to be wakeup capable?
> >>
> >> 3.4 major works just fine for me.
> >
> > Can you try with the fixes branch that Olof just merged?
>
> I tried merging the fixes branch on 3.5-rc1 as well as latest
> mainline and both didn't work.
>
> > If it's the UART wake-up events, there's a patch that should
> > help.
> >
> > Tony
>
The patch referenced here helps:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg69596.html
DSS crashes during wakeup from suspend.
-Tero
next prev parent reply other threads:[~2012-06-08 13:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 10:35 suspend broken on 3.5-rc1? Rajendra Nayak
2012-06-08 10:56 ` Tony Lindgren
2012-06-08 12:25 ` Rajendra Nayak
2012-06-08 13:05 ` Tero Kristo [this message]
2012-06-08 13:16 ` Rajendra Nayak
2012-06-12 12:01 ` Rajendra Nayak
2012-07-11 21:06 ` Omar Ramirez Luna
2012-07-11 21:42 ` Kevin Hilman
2012-07-11 23:58 ` Omar Ramirez Luna
2012-07-12 5:27 ` Rajendra Nayak
2012-07-12 8:31 ` Tero Kristo
2012-07-12 19:49 ` Omar Ramirez Luna
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=1339160732.2091.47.camel@sokoban \
--to=t-kristo@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
--cc=tony@atomide.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox