All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: jean.pihet@newoldbits.com
Cc: 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.com>,
	magnus.damm@gmail.com, Todd Poynor <toddpoynor@google.com>,
	linux-arm <linux-arm-kernel@lists.infradead.org>,
	Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH 2/6] OMAP2+: omap_hwmod: manage the wake-up latency constraints
Date: Tue, 13 Dec 2011 15:46:47 -0800	[thread overview]
Message-ID: <87hb14t4pk.fsf@ti.com> (raw)
In-Reply-To: <1323706701-6627-3-git-send-email-j-pihet@ti.com> (jean pihet's message of "Mon, 12 Dec 2011 17:18:17 +0100")

jean.pihet@newoldbits.com writes:

> From: Jean Pihet <j-pihet@ti.com>
>
> Hwmod is queried from the OMAP_PM layer to manage the power domains

nit: changelog needs a refresh as this isn't called from OMAP PM layer.

> wake-up latency constraints. Hwmod retrieves the correct power domain
> and if it exists it calls the corresponding power domain function.
>
> Tested on OMAP3 Beagleboard and OMAP4 Pandaboard in RET/OFF using wake-up
> latency constraints on MPU, CORE and PER.
>
> Signed-off-by: Jean Pihet <j-pihet@ti.com>

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/6] OMAP2+: omap_hwmod: manage the wake-up latency constraints
Date: Tue, 13 Dec 2011 15:46:47 -0800	[thread overview]
Message-ID: <87hb14t4pk.fsf@ti.com> (raw)
In-Reply-To: <1323706701-6627-3-git-send-email-j-pihet@ti.com> (jean pihet's message of "Mon, 12 Dec 2011 17:18:17 +0100")

jean.pihet at newoldbits.com writes:

> From: Jean Pihet <j-pihet@ti.com>
>
> Hwmod is queried from the OMAP_PM layer to manage the power domains

nit: changelog needs a refresh as this isn't called from OMAP PM layer.

> wake-up latency constraints. Hwmod retrieves the correct power domain
> and if it exists it calls the corresponding power domain function.
>
> Tested on OMAP3 Beagleboard and OMAP4 Pandaboard in RET/OFF using wake-up
> latency constraints on MPU, CORE and PER.
>
> Signed-off-by: Jean Pihet <j-pihet@ti.com>

Kevin

  reply	other threads:[~2011-12-13 23:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 16:18 [PATCH v5 0/6] PM QoS: implement the OMAP low level constraints management code jean.pihet
2011-12-12 16:18 ` jean.pihet at newoldbits.com
2011-12-12 16:18 ` [PATCH 1/6] OMAP2+: powerdomain: control power domains next state jean.pihet
2011-12-12 16:18 ` jean.pihet
2011-12-12 16:18   ` jean.pihet at newoldbits.com
2011-12-12 16:18 ` [PATCH 2/6] OMAP2+: omap_hwmod: manage the wake-up latency constraints jean.pihet
2011-12-12 16:18 ` jean.pihet
2011-12-12 16:18   ` jean.pihet at newoldbits.com
2011-12-13 23:46   ` Kevin Hilman [this message]
2011-12-13 23:46     ` Kevin Hilman
2011-12-12 16:18 ` [PATCH 3/6] OMAP: PM: register to the per-device PM QoS framework jean.pihet
2011-12-12 16:18   ` jean.pihet at newoldbits.com
2011-12-12 16:18 ` jean.pihet
2011-12-12 16:18 ` [PATCH 4/6] OMAP3: cpuidle: next C-state decision depends on the PM QoS MPU and CORE constraints jean.pihet
2011-12-12 16:18   ` jean.pihet at newoldbits.com
2011-12-13 23:49   ` Kevin Hilman
2011-12-13 23:49     ` Kevin Hilman
2011-12-12 16:18 ` jean.pihet
2011-12-12 16:18 ` [PATCH 5/6] OMAP3: update cpuidle latency and threshold figures jean.pihet
2011-12-12 16:18   ` jean.pihet at newoldbits.com
2011-12-12 16:18 ` jean.pihet
2011-12-12 16:18 ` [PATCH 6/6] OMAP3: powerdomain data: add wake-up latency figures jean.pihet
2011-12-12 16:18 ` jean.pihet
2011-12-12 16:18   ` jean.pihet at newoldbits.com
2011-12-13 23:53 ` [PATCH v5 0/6] PM QoS: implement the OMAP low level constraints management code Kevin Hilman
2011-12-13 23:53   ` Kevin Hilman
2011-12-14 14:55   ` Jean Pihet
2011-12-14 14:55     ` Jean Pihet
  -- strict thread matches above, loose matches on Subject: below --
2011-12-14 14:51 [PATCH v6 " jean.pihet
2011-12-14 14:51 ` [PATCH 2/6] OMAP2+: omap_hwmod: manage the wake-up latency constraints jean.pihet
2011-12-14 14:51   ` jean.pihet at newoldbits.com
2011-12-19 21:11   ` Paul Walmsley
2011-12-19 21:11     ` Paul Walmsley
2011-10-19 13:50 [PATCH v4 0/6] PM QoS: implement the OMAP low level constraints management code jean.pihet
2011-10-19 13:50 ` [PATCH 2/6] OMAP2+: omap_hwmod: manage the wake-up latency constraints 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=87hb14t4pk.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=j-pihet@ti.com \
    --cc=jean.pihet@newoldbits.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=magnus.damm@gmail.com \
    --cc=paul@pwsan.com \
    --cc=rjw@sisk.pl \
    --cc=toddpoynor@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.