From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] OMAP PM cleanups for v3.10
Date: Tue, 09 Apr 2013 16:13:29 -0700 [thread overview]
Message-ID: <87ehej1ena.fsf@linaro.org> (raw)
Tony,
Here's the final set of OMAP PM cleanups for v3.10. This is a small set
of cleanups from Santosh to consolidate and prepare for OMAP5 PM additions.
It's based on your cleanup-v2 branch.
Kevin
The following changes since commit c309f7f46167e85d1aae2fd31f23e7d2b5cdfbe0:
Merge branch 'for_3.10/omap_generic_cleanup_v2' of git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux into omap-for-v3.10/cleanup-v2 (2013-03-28 14:45:31 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git tags/omap-pm-v3.10/cleanup/pm
for you to fetch changes up to 705814b5ea6ff69d4da8ad581c3da5d26d1eae83:
ARM: OMAP4+: PM: Consolidate OMAP4 PM code to re-use it for OMAP5 (2013-04-09 10:53:06 -0700)
----------------------------------------------------------------
OMAP PM cleanups for v3.10
----------------------------------------------------------------
Santosh Shilimkar (4):
ARM: OMAP4: PM: Avoid expensive cpu_suspend() path for all CPU power states except off
ARM: OMAP4+: PM: Consolidate MPU subsystem PM code for re-use
ARM: OMAP4+: Make secondary_startup function name more consistent
ARM: OMAP4+: PM: Consolidate OMAP4 PM code to re-use it for OMAP5
arch/arm/mach-omap2/common.h | 4 +-
arch/arm/mach-omap2/omap-headsmp.S | 8 ++--
arch/arm/mach-omap2/omap-mpuss-lowpower.c | 69 +++++++++++++++++++++++++------
arch/arm/mach-omap2/omap-smp.c | 6 +--
arch/arm/mach-omap2/pm44xx.c | 58 +++++++++++++++++++++-----
5 files changed, 113 insertions(+), 32 deletions(-)
next reply other threads:[~2013-04-09 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 23:13 Kevin Hilman [this message]
2013-04-10 18:14 ` [GIT PULL] OMAP PM cleanups for v3.10 Tony Lindgren
2013-04-23 17:59 ` Olof Johansson
2013-04-23 18:47 ` Kevin Hilman
2013-05-16 14:02 ` Kevin Hilman
2013-05-16 15:30 ` Tony Lindgren
2013-05-21 6:07 ` Olof Johansson
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=87ehej1ena.fsf@linaro.org \
--to=khilman@linaro.org \
--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).