From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/11] OMAP2+: clock: add clockfw autoidle for iclks, OMAP2xxx
Date: Fri, 18 Feb 2011 11:05:47 +0530 [thread overview]
Message-ID: <cf17c43dfb21a50236058918ae984a65@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1102161551400.29817@utopia.booyaka.com>
> -----Original Message-----
> From: Paul Walmsley [mailto:paul at pwsan.com]
> Sent: Thursday, February 17, 2011 4:35 AM
> To: Rajendra Nayak
> Cc: linux-omap at vger.kernel.org; linux-arm-kernel at lists.infradead.org
> Subject: RE: [PATCH 00/11] OMAP2+: clock: add clockfw autoidle for
iclks, OMAP2xxx
>
> On Wed, 16 Feb 2011, Rajendra Nayak wrote:
>
> > Boot-tested on 3430sdp/4430sdp, with CONFIG_PM and with !CONFIG_PM.
> > suspend-offmode tested on 3430sdp and suspend-retmode on 4430sdp (with
> > some out-of-tree patches)
>
> Thanks, will add Tested-by:s.
>
> > Dynamic idle testing on 3430sdp showed me some very jerky debug
console
> > the moment a 'echo 1 > /debug/pm_debug/sleep_while_idle' is done. This
> > however seems to be the case even on 2.6.38-rc4 and not related to the
> > current patch series.
>
> Does enabling CONFIG_OMAP2_DSS resolve the problem you're seeing?
Maybe, will try it out. Thanks for the tip.
>
> > Will debug further, but seems to some 3430sdp specific issue, since
you
> > did not see it on Beagleboard and seems it is not seen on OMAP3 zoom's
> > either. Just out of curiosity, what dynamic-idle state where you able
to
> > achieve on Beagle?
>
> Full chip off. I use omap2plus_defconfig, sometimes with
CONFIG_OMAP2_DSS
> depending on personal mood and what's being tested. I boot to a shell
and
> run the commands at the end of this message (some of which are probably
> superfluous).
Ok, thanks.
>
>
> - Paul
>
>
> echo 1 > /debug/pm_debug/sleep_while_idle
> echo 1 > /debug/pm_debug/enable_off_mode
> echo 5 > /sys/devices/platform/omap/omap_uart.0/sleep_timeout
> echo 5 > /sys/devices/platform/omap/omap_uart.1/sleep_timeout
> echo 5 > /sys/devices/platform/omap/omap_uart.2/sleep_timeout
> echo enabled >
/sys/devices/platform/omap/omap_uart.0/tty/ttyO0/power/wakeup
> echo enabled >
/sys/devices/platform/omap/omap_uart.1/tty/ttyO1/power/wakeup
> echo enabled >
/sys/devices/platform/omap/omap_uart.2/tty/ttyO2/power/wakeup
>
next prev parent reply other threads:[~2011-02-18 5:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 6:52 [PATCH 00/11] OMAP2+: clock: add clockfw autoidle for iclks, OMAP2xxx Paul Walmsley
2011-02-16 6:52 ` [PATCH 01/11] OMAP2+: clock: disable autoidle on all clocks during clock init Paul Walmsley
2011-02-16 6:52 ` [PATCH 02/11] OMAP2: clock: add DPLL autoidle support Paul Walmsley
2011-02-16 6:52 ` [PATCH 03/11] OMAP2xxx: clock: add clockfw autoidle support for APLLs Paul Walmsley
2011-02-16 6:52 ` [PATCH 04/11] OMAP2+: clock: comment that osc_ck/osc_sys_ck should use clockfw autoidle control Paul Walmsley
2011-02-16 6:52 ` [PATCH 05/11] OMAP2+: clock: add interface clock type code with autoidle support Paul Walmsley
2011-02-16 6:52 ` [PATCH 06/11] OMAP2420: clock: add sdrc_ick Paul Walmsley
2011-02-16 6:52 ` [PATCH 07/11] OMAP2420: clock: use autoidle clkops for all autoidle-controllable interface clocks Paul Walmsley
2011-02-16 6:52 ` [PATCH 08/11] OMAP2430/3xxx: clock: add modem clock autoidle support Paul Walmsley
2011-02-16 6:52 ` [PATCH 09/11] OMAP2430: clock: use autoidle clkops for all autoidle-controllable interface clocks Paul Walmsley
2011-02-16 6:52 ` [PATCH 10/11] OMAP3: " Paul Walmsley
2011-02-16 6:52 ` [PATCH 11/11] OMAP2/3: PM: remove manual CM_AUTOIDLE bit setting in mach-omap2/pm*xx.c Paul Walmsley
2011-02-16 9:37 ` [PATCH 00/11] OMAP2+: clock: add clockfw autoidle for iclks, OMAP2xxx Rajendra Nayak
2011-02-16 22:14 ` Paul Walmsley
2011-02-18 5:33 ` Rajendra Nayak
2011-02-16 11:15 ` Rajendra Nayak
2011-02-16 23:05 ` Paul Walmsley
2011-02-18 5:35 ` Rajendra Nayak [this message]
2011-03-01 20:58 ` Kevin Hilman
2011-03-08 3:06 ` Paul Walmsley
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=cf17c43dfb21a50236058918ae984a65@mail.gmail.com \
--to=rnayak@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).