From: Kevin Hilman <khilman@deeprootsystems.com>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-omap@vger.kernel.org
Subject: Re: BeagleBoard not resuming from uart with latest pm-core ?
Date: Wed, 10 Nov 2010 09:32:53 -0800 [thread overview]
Message-ID: <87pqudaxtm.fsf@deeprootsystems.com> (raw)
In-Reply-To: <AANLkTi=Dzv2XE-X_z6yiCaRjgWrST5QGDE9dFDnDy9pT@mail.gmail.com> (Jean Pihet's message of "Wed, 10 Nov 2010 17:07:08 +0100")
Jean Pihet <jean.pihet@newoldbits.com> writes:
> l-o is currently broken wrt to suspend and idle.
> Solutions are being worked on for the moment.
>
> Kevin, are there solutions available yet?
The solution to your previous problem (ensuring runtime PM transitions
work during system PM) is included in my pm-core branch, but is not yet
the final solution. I've been disussing this issue with the runtime PM
maintainers for a final solution. Until then, I will carry this in
pm-core.
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.
Of course, any help debugging these problems is appreciated. I will not
get to debugging this until I catch up on the mailing list backlog.
Kevin
> On Wed, Nov 10, 2010 at 4:44 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Hello,
>>
>> I've updated my tree to the last pm-core branch today (I'm at commit
>> 42289e226ec996a13ab8a2aaef5ad9dda61ee57e), and I've built the
>> omap2plus_defconfig with no change (except adding an initramfs). On my
>> BeagleBoard, I enable the wakeup from UART
>> in /sys/devices/platform/omap/omap-hsuart.2/tty/ttyO2/power/wakeup,
>> then trigger suspend to RAM. It enters suspend to RAM, but then
>> it doesn't wakeup when I send data through the UART.
>>
>> Is it a known problem, or is again a mistake on my side ?
>>
>> Thanks,
>>
>> Thomas
>> --
>> Thomas Petazzoni, Free Electrons
>> Kernel, drivers, real-time and embedded Linux
>> development, consulting, training and support.
>> http://free-electrons.com
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-10 17:32 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 [this message]
2010-11-11 11:41 ` Peter 'p2' De Schrijver
2010-11-11 16:00 ` Kevin Hilman
2010-11-15 10:50 ` Thomas Petazzoni
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=87pqudaxtm.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-omap@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).