From: Tyler <tyler@bmsacoustics.com>
To: linux-omap@vger.kernel.org
Subject: Re: Serial console not working after waking up from sleep
Date: Thu, 22 Jul 2010 21:09:04 +0000 (UTC) [thread overview]
Message-ID: <loom.20100722T224314-889@post.gmane.org> (raw)
In-Reply-To: D2943F03B81C9C458E44DFB213905E02B65BA040@dlee04.ent.ti.com
Sapiens, Rene <rene.sapiens <at> ti.com> writes:
>
> You can do a telnet to the device... you should be able to work with it but
your serial session will show the garbage.
>
> Regards,
> Rene
>
Hello,
I am in essentially the same position, but currently working off of the pm-head
branch.
I am just using an initramfs, and have tried a few variations.
With no_console_suspend set, I can trigger a wakeup using the
wakeup_timer_seconds. The power usage goes back to the pre-suspend level, and I
see text indicating a successful wakeup, but the console never comes back.
Without no_console_suspend set, I can trigger the wakeup again with
wakeup_timer_seconds, a console prompt comes back, but is unresponsive.
I saw Rene's response about using Telnet, but this implies that there is an
ethernet interface available. I have a custom board that only has a serial
interface for external visibility, so at this point I lose insight into what is
happening on the board.
I have two questions, if people would be so willing to oblige:
1) Does anyone know why the console doesn't come back after wakeup? Is this
something that may work in the future?
2) Does the console freezing mean that the other COM ports also don't work?
Would communication on other interfaces continue to work? For example, a GPS
plugged into one of the other COM ports?
Thanks,
Tyler
prev parent reply other threads:[~2010-07-22 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 3:21 Serial console not working after waking up from sleep Han Wang
2010-06-16 6:09 ` Michael Trimarchi
2010-06-16 8:43 ` Jean Pihet
2010-06-16 14:37 ` Han Wang
2010-06-16 14:40 ` Han Wang
2010-06-16 14:47 ` Michael Trimarchi
2010-06-16 20:53 ` Sapiens, Rene
2010-07-22 21:09 ` Tyler [this message]
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=loom.20100722T224314-889@post.gmane.org \
--to=tyler@bmsacoustics.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