linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jean.pihet@newoldbits.com
To: khilman@ti.com, paul@pwsan.com, Vibhore Vardhan <vvardhan@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Vishwanath BS <vishwanath.bs@ti.com>,
	rnayak@ti.com
Cc: linux-omap@vger.kernel.org, Jean Pihet <j-pihet@ti.com>
Subject: [RFC PATCH 0/2] OMAP: PM: add devices wakeup latency constraints APIs
Date: Thu, 10 Feb 2011 20:23:25 +0100	[thread overview]
Message-ID: <1297365807-12143-1-git-send-email-j-pihet@ti.com> (raw)

From: Jean Pihet <j-pihet@ti.com>

- Implement OMAP PM layer omap_pm_set_max_dev_wakeup_lat API.
- Created arch/arm/plat-omap/omap-pm-constraints.c file from 
arch/arm/plat-omap/omap-pm-noop.c and the associated Kconfig option
OMAP_PM_CONSTRAINTS.

This code is an early submission in RFC state and is for review only.
Testing is on-going.

ToDo:
- implement the API for the SDMA device (omap_pm_set_max_sdma_lat),
- change the power domains latency figures to some more realistic values,
- add the hook to the existing kernel PM QoS interfaces (cpu_dma_latency),
   cf. Documentation/power/pm_qos_interface.txt

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             |  176 +++++++++++++-
 arch/arm/mach-omap2/powerdomain.h             |   31 +++
 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      |  344 +++++++++++++++++++++++++
 arch/arm/plat-omap/omap_device.c              |   28 ++
 10 files changed, 710 insertions(+), 3 deletions(-)
 create mode 100644 arch/arm/plat-omap/omap-pm-constraints.c

-- 
1.7.2.3


             reply	other threads:[~2011-02-10 19:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 19:23 jean.pihet [this message]
2011-02-10 19:23 ` [PATCH 1/2] OMAP PM: create a PM layer plugin for the devices wakeup latency constraints jean.pihet
2011-02-10 19:23 ` [PATCH 2/2] OMAP: PM: implement devices wakeup latency constraints APIs jean.pihet
2011-02-11 10:23   ` Gulati, Shweta
2011-02-11 16:31     ` Jean Pihet
2011-02-15  9:35   ` Vishwanath Sripathy
2011-02-15 13:52     ` Jean Pihet
2011-02-16 10:49       ` Vishwanath Sripathy
2011-02-16 12:58         ` Pihet-XID, Jean
2011-02-18 11:04   ` Rajendra Nayak
2011-02-18 15:03     ` 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=1297365807-12143-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=paul@pwsan.com \
    --cc=rnayak@ti.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=vishwanath.bs@ti.com \
    --cc=vvardhan@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).