From: Vladimir Pantelic <pan@nt.tu-darmstadt.de>
To: Mike Rapoport <mike@compulab.co.il>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
Peter Tseng <tsenpet09@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Han Wang <hw342@cornell.edu>
Subject: Re: Overo serial problems after resume, vs. Beagleboard
Date: Tue, 22 Jun 2010 11:06:38 +0200 [thread overview]
Message-ID: <4C207D1E.7010508@nt.tu-darmstadt.de> (raw)
In-Reply-To: <4C207A9C.7070309@compulab.co.il>
Mike Rapoport wrote:
> Kevin Hilman wrote:
>> Peter Tseng<tsenpet09@gmail.com> writes:
>>
>>> I am seeing some discrepancies between the Overo (I believe I have a
>>> Water) and the Beagleboard (I have a Rev. B5) when resuming after a
>>> suspend to RAM.
>>
>> Not that it is much comfort, but I have the same problem on Overo but
>> don't see it on any other OMAP3 board.
>>
>> I have yet to debug this particular issue further.
>
> I had the same issue on CM-T35 and when I've disabled CONFIG_CPU_IDLE in the
> kernel configuration the issue disappeared. Maybe it'll be of some help.
I have that disabled as well on my debug builds, but only in order not to have
1 char swallowed when the serial wakes the cpu... Still might be worth a
try on overo/summit
next prev parent reply other threads:[~2010-06-22 9:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 17:04 Overo serial problems after resume, vs. Beagleboard Peter Tseng
2010-06-21 17:40 ` Kevin Hilman
2010-06-22 7:34 ` Robert Lukassen
2010-06-22 8:55 ` Mike Rapoport
2010-06-22 9:06 ` Vladimir Pantelic [this message]
2010-06-22 9:37 ` Robert Lukassen
2010-06-22 14:31 ` Kevin Hilman
2010-06-23 5:46 ` Mike Rapoport
2010-08-10 23:57 ` 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=4C207D1E.7010508@nt.tu-darmstadt.de \
--to=pan@nt.tu-darmstadt.de \
--cc=hw342@cornell.edu \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=mike@compulab.co.il \
--cc=tsenpet09@gmail.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