From: Nishanth Menon <nm@ti.com>
To: l-o <linux-omap@vger.kernel.org>
Cc: Kevin H <khilman@deeprootsystems.com>, Tony <tony@atomide.com>,
Nishanth Menon <nm@ti.com>
Subject: [PATCH 0/3 v2] omap: opp: Add opp data
Date: Tue, 19 Oct 2010 20:02:20 -0500 [thread overview]
Message-ID: <1287536543-9729-1-git-send-email-nm@ti.com> (raw)
Rev2 of the original series since opp layer is moved to power for-next tree:
http://marc.info/?l=linux-omap&m=128458780403670&w=2
This series introduces a layer to manage Operating Performance Points (OPPs)
for OMAP SoCs.
Based on kernel.org commit 51ea8a8.
Depends on OPP layer patch from Rafael's tree:
http://git.kernel.org/?p=linux/kernel/git/rafael/suspend-2.6.git;a=commit;h=56149b574181d98aedf97f1f2d91d05ab261db41
Note:
Tony, for applying on l-o, the following conflicts:
arch/arm/mach-omap2/Kconfig -> few additional changes to ARCH_OMAP{3,4}
not in kernel.org yet.
arch/arm/mach-omap2/io.c - hwmodint of omap4 is introduced
Conflicts are trivial and if necessary, I can post one rebased to l-o
Patch "omap4: opp: add OPP table data" is based off the OPP data from
http://dev.omapzoom.org/?p=santosh/kernel-omap4-base.git;a=blob;f=arch/arm/mach-omap2/opp44xx_data.c;h=252e3d0cb6050a64f390b9311c1c4977d74f762a;hb=refs/heads/omap4_next
Kevin Hilman (1):
OMAP3: remove OPP interfaces from OMAP PM layer
Nishanth Menon (2):
omap: opp: add OMAP3 OPP table data and common init
omap4: opp: add OPP table data
arch/arm/mach-omap2/Kconfig | 2 +
arch/arm/mach-omap2/Makefile | 2 +
arch/arm/mach-omap2/io.c | 3 +-
arch/arm/mach-omap2/opp.c | 142 +++++++++++++++++++++++++++++
arch/arm/mach-omap2/opp3xxx_data.h | 82 +++++++++++++++++
arch/arm/mach-omap2/opp4xxx_data.h | 37 ++++++++
arch/arm/mach-omap2/pm.c | 6 +
arch/arm/mach-omap2/pm.h | 8 ++
arch/arm/plat-omap/include/plat/omap-pm.h | 31 ++----
arch/arm/plat-omap/omap-pm-noop.c | 11 +--
10 files changed, 291 insertions(+), 33 deletions(-)
create mode 100644 arch/arm/mach-omap2/opp.c
create mode 100644 arch/arm/mach-omap2/opp3xxx_data.h
create mode 100644 arch/arm/mach-omap2/opp4xxx_data.h
Regards,
Nishanth Menon
next reply other threads:[~2010-10-20 1:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 1:02 Nishanth Menon [this message]
2010-10-20 1:02 ` [PATCH 1/3 v2] omap: opp: add OMAP3 OPP table data and common init Nishanth Menon
2010-10-20 1:02 ` [PATCH 2/3 v2] omap4: opp: add OPP table data Nishanth Menon
2010-10-20 1:02 ` [PATCH 3/3 v2] OMAP3: remove OPP interfaces from OMAP PM layer Nishanth Menon
2010-11-04 23:20 ` Tony Lindgren
2010-11-04 23:13 ` [PATCH 2/3 v2] omap4: opp: add OPP table data Tony Lindgren
2010-11-05 0:05 ` Menon, Nishanth
2010-11-04 23:10 ` [PATCH 1/3 v2] omap: opp: add OMAP3 OPP table data and common init Tony Lindgren
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=1287536543-9729-1-git-send-email-nm@ti.com \
--to=nm@ti.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox