From: Kevin Hilman <khilman@deeprootsystems.com>
To: Rajendra Nayak <rnayak@ti.com>, Richard Woodruff <r-woodruff2@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: OMAP3 PM: off-mode during idle, problem with UART1 console
Date: Tue, 16 Jun 2009 14:05:02 -0700 [thread overview]
Message-ID: <87iqiv28ld.fsf@deeprootsystems.com> (raw)
Rajendra, Richard,
Hoping you can shed some light, or give me some direction on where to
debug this further...
With the latest PM branch, I've notice that off-while idle isn't
working on the SDP, but the same kernel works fine on the RX51.
RET-while-idle works fine on both. This is with CPUidle disabled, so
just using the default idle where MPU and CORE are changed together.
More specifically, it seems to be the UART1 (CORE) console that never
comes back from off-while-idle, but the UART3 (PER) console on RX51
works.
On SDP, if I
# echo 1 > /sys/power/enable_off_mode
# echo 1 > /sys/power/voltage_off_while_idle
# echo 1 > /sys/power/sleep_while_idle
After the UART inactivty timeout of 5 seconds, I start to see the
sys_off_mode LED toggling between red and green with system timer
wakeups.
If I then push a key on the UART1 console, the LED goes green, stays
for the 5 second UART inactivity and then goes back to toggling
red/green again. However, I never get my console back and never see
the characters on my console.
If I keep typing, I keep the system from going back off (based on
sys_off_mode LED) and as soon as I stop typing long enough for the
inactivity timer to expiere (5 seconds) it goes back into off.
Any ideas what's going on here?
On RX51, the same thing works using UART3.
Kevin
next reply other threads:[~2009-06-16 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 21:05 Kevin Hilman [this message]
2009-06-17 6:11 ` OMAP3 PM: off-mode during idle, problem with UART1 console Nayak, Rajendra
2009-06-17 14:38 ` Woodruff, Richard
2009-06-17 15:07 ` Kevin Hilman
2009-06-17 15:06 ` Kevin Hilman
2009-06-19 9:42 ` Nayak, Rajendra
2009-06-19 16:20 ` Kevin Hilman
2009-06-19 16:40 ` Woodruff, Richard
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=87iqiv28ld.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@ti.com \
--cc=rnayak@ti.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