From: jouni.hogander@nokia.com (Högander Jouni)
To: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/4] Refreshed PM workaround patches
Date: Fri, 15 Aug 2008 10:04:18 +0300 [thread overview]
Message-ID: <87zlnerc7h.fsf@trdhcp146196.ntc.nokia.com> (raw)
In-Reply-To: <877iaiu7np.fsf@trdhcp146196.ntc.nokia.com> (ext Högander Jouni's message of "Fri, 15 Aug 2008 09:14:18 +0300")
ext Högander Jouni <jouni.hogander@nokia.com> writes:
> Hi,
>
> One more refreshed PM workaround set. Here are instructions, how to test
> them:
>
> To get Omap into retention, this patch set still depends on:
> 1. ARCH: OMAP: MUSB: Do not block sleep (Felipe Balbi)
>
> Test:
> 1. Apply dependency patch 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.
Please ignore this set. It break 24xx build and patches contains
error. Sorry for this. I will send them again soon.
--
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
prev parent reply other threads:[~2008-08-15 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 6:14 [PATCH 0/4] Refreshed PM workaround patches Högander Jouni
2008-08-15 7:04 ` Högander Jouni [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=87zlnerc7h.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