From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Subject: [PATCH 0/4] OMAP OPP layer
Date: Tue, 10 Aug 2010 17:07:30 -0700 [thread overview]
Message-ID: <1281485254-20704-1-git-send-email-khilman@deeprootsystems.com> (raw)
This series introduces a layer to manage Operating Performance Points (OPPs)
for OMAP SoCs.
Special thanks to Nishanth for doing the bulk of the grunt work for
this series and to Thara for doing significant review, testing and
updates.
Kevin Hilman (1):
omap3: pm: remove OPP interfaces from OMAP PM layer
Nishanth Menon (1):
OMAP: introduce OPP layer for device-specific OPPs
Paul Walmsley (1):
omap: opp: twl/tps: Introduce TWL/TPS-specific code
Thara Gopinath (1):
OMAP: Remove dependency of generic opp layer on cpufreq.
Documentation/arm/OMAP/omap_pm | 93 +++++
arch/arm/mach-omap2/io.c | 3 +-
arch/arm/plat-omap/Makefile | 8 +-
arch/arm/plat-omap/include/plat/omap-pm.h | 31 +-
arch/arm/plat-omap/include/plat/opp.h | 160 ++++++++
arch/arm/plat-omap/include/plat/opp_twl_tps.h | 21 +
arch/arm/plat-omap/omap-pm-noop.c | 11 +-
arch/arm/plat-omap/opp.c | 513 +++++++++++++++++++++++++
arch/arm/plat-omap/opp_twl_tps.c | 41 ++
9 files changed, 847 insertions(+), 34 deletions(-)
create mode 100644 arch/arm/plat-omap/include/plat/opp.h
create mode 100644 arch/arm/plat-omap/include/plat/opp_twl_tps.h
create mode 100644 arch/arm/plat-omap/opp.c
create mode 100644 arch/arm/plat-omap/opp_twl_tps.c
--
1.7.2.1
next reply other threads:[~2010-08-11 0:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 0:07 Kevin Hilman [this message]
2010-08-11 0:07 ` [PATCH 1/4] OMAP: introduce OPP layer for device-specific OPPs Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2010-08-11 0:09 [PATCH 0/4] OMAP OPP layer Kevin Hilman
2010-08-11 0:17 ` 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=1281485254-20704-1-git-send-email-khilman@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.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).