From: jean.pihet@newoldbits.com (Jean Pihet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] OMAP: PM: implement devices wakeup latency constraints APIs
Date: Fri, 4 Mar 2011 15:52:53 +0100 [thread overview]
Message-ID: <1299250375-26134-1-git-send-email-j-pihet@ti.com> (raw)
Implement OMAP PM layer omap_pm_set_max_dev_wakeup_lat API by
creating similar APIs at the omap_device and omap_hwmod levels. The
omap_hwmod level call is the layer with access to the powerdomain
core, so it is the place where the powerdomain is queried to set and
release the constraints.
NOTE: only works for devices which have been converted to use
omap_device/omap_hwmod.
Longer term, we could possibly remove this API from the OMAP PM layer,
and instead directly use the device level API.
The power domains get the next power state programmed directly in
the registers via pwrdm_wakeuplat_update_pwrst.
Note about PM QOS: the MPU and CORE power domains get the next power
state via cpuidle, which get the strongest wake-up latency constraint
by querying PM QOS. The usage of PM QOS is temporary, until a generic
solution is in place.
Jean Pihet (2):
OMAP PM: create a PM layer plugin for the devices wakeup latency
constraints
OMAP: PM: implement devices wakeup latency constraints APIs
arch/arm/mach-omap2/omap_hwmod.c | 62 +++++-
arch/arm/mach-omap2/powerdomain.c | 197 ++++++++++++++
arch/arm/mach-omap2/powerdomain.h | 39 +++-
arch/arm/mach-omap2/powerdomains3xxx_data.c | 60 ++++
arch/arm/plat-omap/Kconfig | 7 +
arch/arm/plat-omap/Makefile | 1 +
arch/arm/plat-omap/include/plat/omap_device.h | 2 +
arch/arm/plat-omap/include/plat/omap_hwmod.h | 2 +
arch/arm/plat-omap/omap-pm-constraints.c | 358 +++++++++++++++++++++++++
arch/arm/plat-omap/omap_device.c | 28 ++
10 files changed, 754 insertions(+), 2 deletions(-)
create mode 100644 arch/arm/plat-omap/omap-pm-constraints.c
--
1.7.2.3
next reply other threads:[~2011-03-04 14:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 14:52 Jean Pihet [this message]
2011-03-04 14:52 ` [PATCH 1/2] OMAP PM: create a PM layer plugin for the devices wakeup latency constraints Jean Pihet
2011-03-08 1:09 ` Kevin Hilman
2011-03-04 14:52 ` [PATCH 2/2] OMAP: PM: implement devices wakeup latency constraints APIs Jean Pihet
2011-03-08 2:15 ` Kevin Hilman
2011-03-08 15:54 ` Jean Pihet
2011-03-08 17:33 ` Kevin Hilman
2011-03-09 19:19 ` [PATCH 2/2] OMAP: PM: implement devices " Jean Pihet
2011-03-09 19:37 ` Jean Pihet
2011-03-10 19:51 ` Kevin Hilman
2011-03-10 4:03 ` Paul Walmsley
2011-03-10 10:03 ` Jean Pihet
2011-03-10 18:03 ` 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=1299250375-26134-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;
as well as URLs for NNTP newsgroup(s).