From: khilman@ti•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4
Date: Thu, 08 Mar 2012 10:27:17 -0800 [thread overview]
Message-ID: <87sjhjaqyi.fsf@ti.com> (raw)
In-Reply-To: <CAKd1q9rq67gUyXn+rOL348YwaYQiqHR8UQCSd68fpxhZHHsYGA@mail.gmail.com> (Luciano Coelho's message of "Thu, 8 Mar 2012 14:21:43 +0200")
Hi Luca,
"Coelho, Luciano" <coelho@ti•com> writes:
[...]
> I can't get ttyO2 wakeup to work on my Blaze with 3.3-rc5. It works
> fine with 3.2.
I assume you mean wakeup from system-wide suspend (echo mem > /sys/power/state)?
Are you enabling UART wakeups?
They are disabled by default, so you need to:
echo enabled > /sys/devices/platform/omap/omap_uart.2/tty/ttyO2/power/wakeup
It may work in v3.2 due to the fact that the UART runtime PM had the
unintended side-effect of essentially disabling MPU and CORE PM. With
that bug fixed and MPU & CORE actually hitting low power states, you'll
need to ensure UART wakeups are enabled.
If you're already enabling wakeups and this still isn't working, try
adding 'no_console_suspend' to the kernel cmdline, try a suspend/resume
and post the console output.
Thanks,
Kevin
next prev parent reply other threads:[~2012-03-08 18:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 9:38 [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4 Paul Walmsley
2012-02-02 9:38 ` [PATCH 1/2] ARM: OMAP2+: PM: share clkdms_setup() across OMAP2, 3, 4 Paul Walmsley
2012-02-02 9:38 ` [PATCH 2/2] ARM: OMAP2+: PM: share some suspend-related functions " Paul Walmsley
2012-02-02 11:25 ` [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4 Shilimkar, Santosh
2012-02-02 18:38 ` Kevin Hilman
2012-02-02 18:40 ` Paul Walmsley
2012-02-02 20:29 ` Paul Walmsley
2012-03-08 12:21 ` Coelho, Luciano
2012-03-08 18:18 ` Paul Walmsley
2012-03-08 18:27 ` Kevin Hilman [this message]
2012-03-08 18:47 ` Luciano Coelho
2012-03-08 18:55 ` Paul Walmsley
2012-03-08 19:05 ` Luciano Coelho
2012-03-08 21:21 ` Kevin Hilman
2012-03-09 6:15 ` Luciano Coelho
2012-03-09 15:23 ` 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=87sjhjaqyi.fsf@ti.com \
--to=khilman@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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