From: "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com>
To: ext Kevin Hilman <khilman@deeprootsystems.com>
Cc: Jean Pihet <jean.pihet@newoldbits.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: BeagleBoard not resuming from uart with latest pm-core ?
Date: Thu, 11 Nov 2010 13:41:53 +0200 [thread overview]
Message-ID: <20101111114153.GP16966@nokia.com> (raw)
In-Reply-To: <87pqudaxtm.fsf@deeprootsystems.com>
On Wed, Nov 10, 2010 at 06:32:53PM +0100, ext Kevin Hilman wrote:
> 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
N900 uses UART3 as its console... UART2 is bluetooth iirc.
CHeers,
Peter.
next prev parent reply other threads:[~2010-11-11 11:42 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 [this message]
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=20101111114153.GP16966@nokia.com \
--to=peter.de-schrijver@nokia.com \
--cc=jean.pihet@newoldbits.com \
--cc=khilman@deeprootsystems.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 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.