public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Kevin Hilman <khilman@ti.com>, Rajendra Nayak <rnayak@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>
Subject: [PATCH 0/2] ARM: OMAP2+: PM: miscellaneous powerdomain-related improvements
Date: Mon, 30 Jan 2012 02:43:12 -0700	[thread overview]
Message-ID: <20120130093931.11027.31048.stgit@dusk> (raw)

This series optimizes some of the powerdomain-related code in
arch/arm/mach-omap2/pm*, and fixes a bug or two.  These were noticed while
working on the functional powerstate code.

Rajendra and Santosh, if you have a spare moment, could you please
peek at the OMAP4 LOWPOWERSTATECHANGE part of the second patch?  It
makes sense to me in theory, but you both would probably know better
than I :-)

Kevin, want to take this series (assuming folks are happy with it) ?

Tested dynamic idle with and without CPUIdle, with and without
off-mode, on a Beagleboard 35xx.

This series is available via git at git://git.pwsan.com/linux-2.6 in
the branch "pm_cleanup_3.4".


- Paul

---

pm_cleanup_3.4
   text	   data	    bss	    dec	    hex	filename
6592771	 678492	5590684	12861947	 c441fb	vmlinux.orig
6592771	 678492	5590684	12861947	 c441fb	vmlinux.patched

Paul Walmsley (2):
      ARM: OMAP3: PM: remove superfluous calls to pwrdm_clear_all_prev_pwrst()
      ARM: OMAP2+: PM: clean up omap_set_pwrdm_state()


 arch/arm/mach-omap2/pm.c     |   39 +++++++++++++++++----------------------
 arch/arm/mach-omap2/pm34xx.c |    5 -----
 2 files changed, 17 insertions(+), 27 deletions(-)


             reply	other threads:[~2012-01-30  9:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30  9:43 Paul Walmsley [this message]
2012-01-30  9:43 ` [PATCH 1/2] ARM: OMAP3: PM: remove superfluous calls to pwrdm_clear_all_prev_pwrst() Paul Walmsley
2012-01-30 10:54   ` Shilimkar, Santosh
2012-01-31  0:14   ` Kevin Hilman
2012-01-31  3:53     ` Rajendra Nayak
2012-01-31  6:57     ` Shilimkar, Santosh
2012-01-31  7:15       ` Paul Walmsley
2012-01-31  7:23         ` Shilimkar, Santosh
2012-01-31  7:27           ` Paul Walmsley
2012-01-31  7:34             ` Shilimkar, Santosh
2012-01-31  7:49               ` Paul Walmsley
2012-01-31  8:37                 ` Shilimkar, Santosh
2012-01-31 17:29     ` Kevin Hilman
2012-02-01 19:27       ` Paul Walmsley
2012-02-02  7:13         ` Shilimkar, Santosh
2012-02-02  8:33           ` Paul Walmsley
2012-02-02  8:59             ` Shilimkar, Santosh
2012-02-02 10:05               ` Paul Walmsley
2012-02-02 10:17                 ` Shilimkar, Santosh
2012-02-02 15:24                   ` Shilimkar, Santosh
2012-02-02 19:59                     ` Paul Walmsley
2012-02-02 18:14         ` Kevin Hilman
2012-01-30  9:43 ` [PATCH 2/2] ARM: OMAP2+: PM: clean up omap_set_pwrdm_state() Paul Walmsley
2012-01-30 12:17   ` Shilimkar, Santosh
2012-01-31  3:46   ` Rajendra Nayak
2012-01-30 21:27 ` [PATCH 0/2] ARM: OMAP2+: PM: miscellaneous powerdomain-related improvements Kevin Hilman
2012-01-31  7:21   ` Tero Kristo
2012-02-01 13:55   ` Tero Kristo

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=20120130093931.11027.31048.stgit@dusk \
    --to=paul@pwsan.com \
    --cc=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@ti.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=t-kristo@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