From: Jouni Hogander <jouni.hogander@nokia.com>
To: linux-omap@vger.kernel.org
Subject: [PATCH 0/7] 34XX: PM: Workarounds to get omap3 to retention 3rd.
Date: Wed, 25 Jun 2008 12:11:49 +0300 [thread overview]
Message-ID: <87ej6lj2ui.fsf@trdhcp146196.ntc.nokia.com> (raw)
Hi,
This patch set contains all workarounds that are needed to get omap3
to retention. Also patch from Tero Kristo to get PM to work if using
serial console is included in this set. Basically all patches in this
set should be reverted one by one as correct fixes are implemented and
applied.
This patch set superseeds earlier version sent 2008-06-17 7:28:35.
To get Omap into retention, this patch set still depends on:
1. ARCH: OMAP: MUSB: Do not block sleep (Felipe Balbi)
2. ARM: OMAP: SmartReflex driver: enable in omap_3430sdp_defconfig (Kalle
Jokiniemi)
3. PRCM: 34XX: Fix wrong shift value used in dpll4_m4x2_ck enable bit
4. Patch which removes control of usbhost_sar_fck from clock tree (Paul
Walmsley will send this soon)
Test:
1. Apply dependency patches and workaround set on top of them
2. Enable disabling/enabling of gpio2-6 and uart clocks on idle:
$ echo 1 > /sys/power/clocks_off_while_idle
3. Try out static suspend:
$ echo mem > /sys/power/state
Wake up from suspend by entering character to serial console. This
should print out:
"Successfully put all powerdomains to target state"
4. Try out dynamic sleep:
$ echo 1 > /sys/power/sleep_while_idle
On Omap3430 SDP board VCORE_EN led can be used as an indicator. If
it starts to blink after a while then Omap enters retention on
idle. To make this work also display needs to be blanked.
--
Jouni Högander
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-06-25 9:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 9:11 Jouni Hogander [this message]
2008-06-25 9:13 ` [PATCH 1/7] 34XX: PM: Workaround to build omap hsmmc as a module Jouni Hogander
2008-06-25 9:50 ` Felipe Balbi
2008-06-25 11:17 ` Gadiyar, Anand
2008-06-25 12:03 ` Felipe Balbi
2008-06-25 12:11 ` Igor Stoppa
2008-06-25 12:40 ` Gadiyar, Anand
2008-06-25 13:23 ` Igor Stoppa
2008-06-26 4:25 ` Gadiyar, Anand
2008-06-26 7:28 ` Felipe Balbi
2008-06-26 8:31 ` Gadiyar, Anand
2008-06-26 13:20 ` Tony Lindgren
2008-06-25 9:13 ` [PATCH 2/7] 34XX: PM: Workaround to enable autoidle for clocks and plls Jouni Hogander
2008-06-26 2:30 ` Paul Walmsley
2008-06-27 8:59 ` Rajendra Nayak
2008-06-27 9:08 ` Högander Jouni
2008-06-25 9:13 ` [PATCH 3/7] 34XX: PM: Workaround to reset all wkdeps Jouni Hogander
2008-06-25 9:13 ` [PATCH 4/7] 34XX: PM: Workaround to check wether any fck is active before entering sleep Jouni Hogander
2008-06-25 9:13 ` [PATCH 5/7] OMAP: PM: Add new sysfs option for disabling clocks when entering idle Jouni Hogander
2008-06-25 9:13 ` [PATCH 6/7] 34XX: PM: Workaround for taking care of gpio clocks Jouni Hogander
2008-06-26 11:54 ` Rajendra Nayak
2008-06-26 12:16 ` Högander Jouni
2008-06-26 12:30 ` Rajendra Nayak
2008-06-26 12:40 ` Högander Jouni
2008-06-25 9:13 ` [PATCH 7/7] Added sleep support to UART Jouni Hogander
2008-06-25 11:38 ` [PATCH 0/7] 34XX: PM: Workarounds to get omap3 to retention 3rd Rajendra Nayak
2008-06-25 11:43 ` Högander Jouni
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=87ej6lj2ui.fsf@trdhcp146196.ntc.nokia.com \
--to=jouni.hogander@nokia.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