From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Jean Pihet <jean.pihet@newoldbits.com>, linux-omap@vger.kernel.org
Subject: Re: BeagleBoard not resuming from uart with latest pm-core ?
Date: Mon, 15 Nov 2010 11:50:05 +0100 [thread overview]
Message-ID: <20101115115005.30b35e75@surf> (raw)
In-Reply-To: <87pqudaxtm.fsf@deeprootsystems.com>
Hello,
On Wed, 10 Nov 2010 09:32:53 -0800
Kevin Hilman <khilman@deeprootsystems.com> wrote:
> The other problem that I'm aware of so far I've only seen on boards
> with UART2 console (beagle, Overo, n900.) The printk messages that
> warn of 'new worst case [de]activate latency" seem to be racing with
> UART disable code. This makes sense, since this printk is printed to
> the UART immediately after the UART is disabled, which is going to
> cause problems with the current approach to UART pm we have in
> mach-omap2/serial.c. I have not yet fully debugged this and found a
> workaround.
Even if I comment the "new worst case deactivate latency" message, my
BeagleBoard still doesn't wake-up from suspend. Here's what I do:
# echo enabled > /sys/class/tty/ttyO2/power/wakeup
# echo mem > /sys/power/state
[ 227.685028] PM: Syncing filesystems ... done.
[ 227.699432] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 227.725524] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[ 227.880706] PM: suspend of devices complete after 117.767 msecs
[ 227.889160] PM: late suspend of devices complete after 2.136 msecs
[ 227.895782] Disabling non-boot CPUs ...
Any idea ?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-11-15 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 15:44 BeagleBoard not resuming from uart with latest pm-core ? Thomas Petazzoni
2010-11-10 16:07 ` Jean Pihet
2010-11-10 17:32 ` Kevin Hilman
2010-11-11 11:41 ` Peter 'p2' De Schrijver
2010-11-11 16:00 ` Kevin Hilman
2010-11-15 10:50 ` Thomas Petazzoni [this message]
2010-11-15 13:13 ` Thomas Petazzoni
2010-11-15 13:54 ` Govindraj
2010-11-15 14:14 ` Thomas Petazzoni
2010-11-16 22:59 ` Kevin Hilman
2010-11-17 7:20 ` Thomas Petazzoni
2010-11-15 19:29 ` 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=20101115115005.30b35e75@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=jean.pihet@newoldbits.com \
--cc=khilman@deeprootsystems.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).