From: jean.pihet@newoldbits.com (jean.pihet at newoldbits.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] OMAP PM: implement the wake-up latency constraints using PM QOS
Date: Mon, 28 Feb 2011 18:41:21 +0100 [thread overview]
Message-ID: <1298914884-16468-1-git-send-email-j-pihet@ti.com> (raw)
From: Jean Pihet <j-pihet@ti.com>
Use the PM QOS framework to set wake-up latency constraints on the MPU and DMA.
Cpuidle for OMAP34xx uses PM QOS to retreive the strongest constraint and to
determine the next state for the MPU and CORE power domains.
As of today only I2C is requesting a constraint, but every omap_device
should be able to do so.
Note: To be replaced by a more generic solution which allows every
device to put a constraint, and which can control all power
domains in the system. This solution is currently under
investigation.
Jean Pihet (3):
OMAP PM: create a PM layer plugin for the devices wakeup latency
constraints
OMAP: implement MPU and DMA wake-up constraints using PM_QOS
OMAP: use PM QOS for wake-up constraints from I2C
arch/arm/plat-omap/Kconfig | 7 +
arch/arm/plat-omap/Makefile | 1 +
arch/arm/plat-omap/i2c.c | 22 ++-
arch/arm/plat-omap/include/plat/omap-pm.h | 96 ++++---
arch/arm/plat-omap/include/plat/omap_device.h | 1 +
arch/arm/plat-omap/omap-pm-constraints.c | 349 +++++++++++++++++++++++++
arch/arm/plat-omap/omap-pm-noop.c | 70 +++---
7 files changed, 469 insertions(+), 77 deletions(-)
create mode 100644 arch/arm/plat-omap/omap-pm-constraints.c
--
1.7.2.3
next reply other threads:[~2011-02-28 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 17:41 jean.pihet at newoldbits.com [this message]
2011-02-28 17:41 ` [PATCH 1/3] OMAP PM: create a PM layer plugin for the devices wakeup latency constraints jean.pihet at newoldbits.com
2011-02-28 17:41 ` [PATCH 2/3] OMAP: implement MPU and DMA wake-up constraints using PM_QOS jean.pihet at newoldbits.com
2011-02-28 17:41 ` [PATCH 3/3] OMAP: use PM QOS for wake-up constraints from I2C jean.pihet at newoldbits.com
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=1298914884-16468-1-git-send-email-j-pihet@ti.com \
--to=jean.pihet@newoldbits.com \
--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