From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: [GIT] pull request: PM CPUidle base support
Date: Wed, 11 Nov 2009 15:02:21 -0800 [thread overview]
Message-ID: <87zl6szmv6.fsf@deeprootsystems.com> (raw)
Tony,
Here's a pull request for the PM CPUidle support. This branch
is based on the previous off-mode branch,
Kevin
The following changes since commit f265dc4c5d39f2bd369d97c87a7bd89061b159d4:
Rajendra Nayak (1):
OMAP3: PM: Program SDRC to send self refresh on timeout of AUTO_CNT
are available in the git repository at:
ssh://master.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git pm-upstream/pm-cpuidle
Jouni Hogander (1):
OMAP3: PM: Use pwrdm_set_next_pwrst instead of set_pwrdm_state in idle loop
Kalle Jokiniemi (1):
OMAP3: PM: CPUidle: fix init sequencing
Kevin Hilman (2):
OMAP3: PM: CPUidle: obey enable_off_mode flag
OMAP3: PM: CPUidle: check activity for C2, C3, correct accounting
Peter 'p2' De Schrijver (2):
OMAP3: PM: CPUidle: Add new lower-latency C1 state
OMAP3: PM: idle: Remove fclk check for idle loop
Rajendra Nayak (2):
OMAP3: PM: CPUidle: base driver and support for C1-C2
OMAP3: PM: CPUidle: support retention and off-mode C-states
Sanjeev Premi (1):
OMAP3: PM: CPUidle: Start C-state definitions from base 0
Tero Kristo (1):
OMAP3: PM: Added resched check into idle calls
arch/arm/mach-omap2/Makefile | 2 +-
arch/arm/mach-omap2/cpuidle34xx.c | 318 +++++++++++++++++++++++++++++++++++++
arch/arm/mach-omap2/pm.h | 4 +
arch/arm/mach-omap2/pm34xx.c | 55 +------
4 files changed, 329 insertions(+), 50 deletions(-)
create mode 100644 arch/arm/mach-omap2/cpuidle34xx.c
reply other threads:[~2009-11-11 23:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87zl6szmv6.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.