linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/10] OMAP: misc PM queue for 2.6.37
Date: Wed, 15 Sep 2010 16:55:36 -0700	[thread overview]
Message-ID: <1284594946-28963-1-git-send-email-khilman@deeprootsystems.com> (raw)

Various OMAP PM related updates targetted for 2.6.37.

Also available in my pm-next branch:
  git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git pm-next

Kevin Hilman (4):
  OMAP3: PM: whitespace cleanup around IO wakeup enable
  OMAP3: PM: move device-specific special cases from PM core into
    CPUidle
  Revert "OMAP: omap_device: add omap_device_is_valid()"
  OMAP: omap_device: make all devices a child of a new parent device

Paul Walmsley (1):
  OMAP clockdomain: initialize clockdomain registers when the
    clockdomain layer starts

Santosh Shilimkar (3):
  omap: pm-debug: Move common debug code to pm-debug.c
  omap: pm-debug: Enable wakeup_timer_milliseconds debugfs entry
  omap: pm: Move set_pwrdm_state routine to common pm.c

Thara Gopinath (2):
  OMAP: PM debugfs removing OMAP3 hardcodings.
  OMAP4: pm.c extensions for OMAP4 support

 arch/arm/mach-omap2/clockdomain.c             |  110 ++++---------------------
 arch/arm/mach-omap2/cpuidle34xx.c             |   50 +++++++++++-
 arch/arm/mach-omap2/pm-debug.c                |   42 ++++++++-
 arch/arm/mach-omap2/pm.c                      |   70 +++++++++++++++-
 arch/arm/mach-omap2/pm.h                      |    4 +-
 arch/arm/mach-omap2/pm34xx.c                  |   99 ++--------------------
 arch/arm/plat-omap/include/plat/common.h      |    3 +-
 arch/arm/plat-omap/include/plat/omap_device.h |    4 +-
 arch/arm/plat-omap/omap_device.c              |   32 +++-----
 9 files changed, 191 insertions(+), 223 deletions(-)

-- 
1.7.2.1

             reply	other threads:[~2010-09-15 23:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 23:55 Kevin Hilman [this message]
2010-09-15 23:55 ` [PATCH 01/10] OMAP3: PM: whitespace cleanup around IO wakeup enable Kevin Hilman
2010-09-15 23:55 ` [PATCH 02/10] OMAP: PM debugfs removing OMAP3 hardcodings Kevin Hilman
2010-09-15 23:55 ` [PATCH 03/10] OMAP3: PM: move device-specific special cases from PM core into CPUidle Kevin Hilman
2010-09-21  7:52   ` Paul Walmsley
2010-09-21 17:00     ` Kevin Hilman
2010-09-23 23:25       ` Paul Walmsley
2010-09-23 23:47         ` Kevin Hilman
2010-09-24  0:16           ` Kevin Hilman
2010-09-15 23:55 ` [PATCH 04/10] OMAP4: pm.c extensions for OMAP4 support Kevin Hilman
2010-09-15 23:55 ` [PATCH 05/10] omap: pm-debug: Move common debug code to pm-debug.c Kevin Hilman
2010-09-15 23:55 ` [PATCH 06/10] omap: pm-debug: Enable wakeup_timer_milliseconds debugfs entry Kevin Hilman
2010-09-15 23:55 ` [PATCH 07/10] omap: pm: Move set_pwrdm_state routine to common pm.c Kevin Hilman
2010-09-15 23:55 ` [PATCH 08/10] OMAP clockdomain: initialize clockdomain registers when the clockdomain layer starts Kevin Hilman
2010-09-15 23:55 ` [PATCH 09/10] Revert "OMAP: omap_device: add omap_device_is_valid()" Kevin Hilman
2010-09-15 23:55 ` [PATCH 10/10] OMAP: omap_device: make all devices a child of a new parent device 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=1284594946-28963-1-git-send-email-khilman@deeprootsystems.com \
    --to=khilman@deeprootsystems.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).