From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: Serial port RTPM/Suspend issues
Date: Tue, 12 Mar 2013 15:41:41 +0000 [thread overview]
Message-ID: <20130312154140.GB20355@linux-sh.org> (raw)
In-Reply-To: <CABYn4szDUQpgsSErNV6e+f8z9-FdpzzZkhafC5qELdK=kWk6=w@mail.gmail.com>
On Tue, Mar 12, 2013 at 04:31:57PM +0100, Bastian Hecht wrote:
> 2013/3/12 Paul Mundt <lethal@linux-sh.org>:
> > On Tue, Mar 12, 2013 at 03:50:42PM +0100, Bastian Hecht wrote:
> >> To avoid confusion, let me add: Garbage is produced when waking, not
> >> in the shutdown process.
> >
> > I assume this is just data left in the FIFO that hasn't been drained that
> > comes back in an undefined state due to losing the clock?
>
> The port hangs after printing a couple of dozens of characters. The
> system itself seems stable - I can log into it using ssh.
> Does this fit with your theory?
>
There are two theories really, residual FIFO data or baud rate generation
issues. Your dozens of characters thing seems to support the former,
given the FIFO size -- the latter would more likely generate a lot more
spew.
> By the way I am using a shallow sleep to test it. Just cpu_do_idle().
Can you see how it goes booting with nohlt? We have seen issues between
BL bit and sleep interactivity before.
next prev parent reply other threads:[~2013-03-12 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 14:41 Serial port RTPM/Suspend issues Bastian Hecht
2013-03-12 14:50 ` Bastian Hecht
2013-03-12 14:54 ` Paul Mundt
2013-03-12 15:31 ` Bastian Hecht
2013-03-12 15:41 ` Paul Mundt [this message]
2013-03-13 10:11 ` Bastian Hecht
2013-03-13 10:31 ` Bastian Hecht
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=20130312154140.GB20355@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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 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.