From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Cc: nm@ti.com, thara@ti.com, b-cousson@ti.com
Subject: [PATCH 00/12] rework OPP layer to handle device-based OPPs
Date: Wed, 16 Jun 2010 17:17:01 -0700 [thread overview]
Message-ID: <1276733833-18510-1-git-send-email-khilman@deeprootsystems.com> (raw)
The current OPP layer is based on a unique identifier (OPP_MPU,
OPP_DSP, OPP_L3) which is not terribly portable or scalable for future
devices.
Since we'd also like to be able to manage OPPs for any device (as
recently agreed upon during an OMAP PM meeting in TI Bangalore[1]), this
patch changes the OPP API to be device-based instead of unique-ID
based. Essentially, this means passing a 'struct device' instead of a
unique ID to determine which set of OPPs to be used.
The main part of this patch is PATCH 08/12 where the OPP API changes
are made. The earlier parts of the series are prep work for this and
the remaining parts are updating users of the OPP API.
Applies on top of current PM branch.
[1] http://omappedia.org/wiki/Proceedings_of_the_PM_SW_Workshop_Jun_2010
Kevin Hilman (12):
OMAP2/3: hwmod: remove '_hwmod' suffix from names
OMAP: hwmod: add class for DSP hwmods
OMAP3: hwmod: add data for OMAP3 IVA2
OMAP: omap_device: ensure hwmod tracks attached omap_device pointer
OMAP: create omap_devices for MPU, DSP, L3
OMAP: voltage: use device_initcall()
OMAP: SR: use device_initcall()
OMAP2: OPP: update API to be device-based
OMAP3: CPUfreq: update to device-based OPP API
OMAP: voltage: update to new device-based OPP API
OMAP: SRF: update to new device-based OPP API
OMAP: SRF: must be initialized before allowing constraints to be set
arch/arm/mach-omap2/cpufreq34xx.c | 180 +++++--------
arch/arm/mach-omap2/devices.c | 2 +
arch/arm/mach-omap2/io.c | 68 ++++-
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 6 +-
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 6 +-
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 49 +++-
arch/arm/mach-omap2/omap_hwmod_common_data.c | 3 +
arch/arm/mach-omap2/omap_hwmod_common_data.h | 1 +
arch/arm/mach-omap2/resource34xx.c | 95 ++++---
arch/arm/mach-omap2/sr_device.c | 2 +-
arch/arm/mach-omap2/voltage.c | 12 +-
arch/arm/plat-omap/cpu-omap.c | 12 +-
arch/arm/plat-omap/include/plat/common.h | 4 +
arch/arm/plat-omap/include/plat/opp.h | 57 ++---
arch/arm/plat-omap/omap-pm-srf.c | 7 +
arch/arm/plat-omap/omap_device.c | 8 +-
arch/arm/plat-omap/opp.c | 396 +++++++++++---------------
17 files changed, 474 insertions(+), 434 deletions(-)
next reply other threads:[~2010-06-17 0:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 0:17 Kevin Hilman [this message]
2010-06-17 0:17 ` [PATCH 01/12] OMAP2/3: hwmod: remove '_hwmod' suffix from names Kevin Hilman
2010-06-17 14:23 ` Kevin Hilman
2010-06-17 0:17 ` [PATCH 02/12] OMAP: hwmod: add class for DSP hwmods Kevin Hilman
2010-06-17 0:17 ` [PATCH 03/12] OMAP3: hwmod: add data for OMAP3 IVA2 Kevin Hilman
2010-06-17 0:17 ` [PATCH 04/12] OMAP: omap_device: ensure hwmod tracks attached omap_device pointer Kevin Hilman
2010-06-17 0:17 ` [PATCH 05/12] OMAP: create omap_devices for MPU, DSP, L3 Kevin Hilman
2010-06-23 11:01 ` Gopinath, Thara
2010-06-23 14:48 ` Kevin Hilman
2010-06-23 15:03 ` Gopinath, Thara
2010-06-23 17:46 ` Kevin Hilman
2010-06-24 6:23 ` Gopinath, Thara
2010-06-24 18:09 ` Kevin Hilman
2010-06-17 0:17 ` [PATCH 06/12] OMAP: voltage: use device_initcall() Kevin Hilman
2010-06-17 0:17 ` [PATCH 07/12] OMAP: SR: " Kevin Hilman
2010-06-17 0:17 ` [PATCH 08/12] OMAP2: OPP: update API to be device-based Kevin Hilman
2010-06-17 0:17 ` [PATCH 09/12] OMAP3: CPUfreq: update to device-based OPP API Kevin Hilman
2010-06-17 0:17 ` [PATCH 10/12] OMAP: voltage: update to new " Kevin Hilman
2010-06-17 0:17 ` [PATCH 11/12] OMAP: SRF: " Kevin Hilman
2010-06-17 0:17 ` [PATCH 12/12] OMAP: SRF: must be initialized before allowing constraints to be set 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=1276733833-18510-1-git-send-email-khilman@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=thara@ti.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;
as well as URLs for NNTP newsgroup(s).