From: jean.pihet@newoldbits.com
To: Kevin Hilman <khilman@ti.com>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
linux-omap@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Paul Walmsley <paul@pwsan.co>
Cc: Jean Pihet <j-pihet@ti.com>
Subject: [PATCH 0/2] OMAP: PM: switch from omap_pm_ functions to PM QoS
Date: Wed, 19 Oct 2011 16:28:49 +0200 [thread overview]
Message-ID: <1319034531-22964-1-git-send-email-j-pihet@ti.com> (raw)
From: Jean Pihet <j-pihet@ti.com>
. Convert the OMAP I2C driver to the PM QoS API for MPU latency constraints
. Remove the latency related functions from OMAP PM in favor of
the generic per-device PM QoS API
Apply on top of the OMAP PM QoS patch set [1].
Based on the pm-qos branch of the linux-pm git tree (3.1.0-rc3), cf. [2].
Tested on OMAP3 Beagleboard (ES2.x) with constraints on MPU, CORE, PER in
RETention and OFF modes.
[1] http://thread.gmane.org/gmane.linux.ports.arm.omap/65971
[2] git://github.com/rjwysocki/linux-pm.git
Jean Pihet (2):
OMAP: convert I2C driver to PM QoS for latency constraints
OMAP: PM: remove the latency related functions from the API
Documentation/arm/OMAP/omap_pm | 55 +++-------------
arch/arm/plat-omap/i2c.c | 20 ------
arch/arm/plat-omap/include/plat/omap-pm.h | 99 -----------------------------
arch/arm/plat-omap/omap-pm-noop.c | 88 -------------------------
drivers/i2c/busses/i2c-omap.c | 30 +++++-----
include/linux/i2c-omap.h | 1 -
6 files changed, 24 insertions(+), 269 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-10-19 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 14:28 jean.pihet [this message]
2011-10-19 14:28 ` [PATCH 1/2] OMAP: convert I2C driver to PM QoS for latency constraints jean.pihet
2011-12-15 0:17 ` Kevin Hilman
2011-10-19 14:28 ` [PATCH 2/2] OMAP: PM: remove the latency related functions from the API jean.pihet
2011-12-15 0:19 ` Kevin Hilman
2011-12-12 16:27 ` [PATCH 0/2] OMAP: PM: switch from omap_pm_ functions to PM QoS Jean Pihet
2011-12-14 14:57 ` Jean Pihet
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=1319034531-22964-1-git-send-email-j-pihet@ti.com \
--to=jean.pihet@newoldbits.com \
--cc=j-pihet@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=paul@pwsan.co \
--cc=rjw@sisk.pl \
/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).