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 v5 0/6] PM QoS: implement the OMAP low level constraints management code
Date: Tue, 13 Dec 2011 15:53:20 -0800 [thread overview]
Message-ID: <87zkewrpu7.fsf@ti.com> (raw)
In-Reply-To: <1323706701-6627-1-git-send-email-j-pihet@ti.com> (jean pihet's message of "Mon, 12 Dec 2011 17:18:15 +0100")
Hi Jean,
jean.pihet@newoldbits.com writes:
> From: Jean Pihet <j-pihet@ti.com>
>
> . Implement the devices wake-up latency constraints using the global
> device PM QoS notification handler which applies the constraints to the
> underlying layer
> . Implement the low level code which controls the power domains next power
> states, through the hwmod and pwrdm layers
> . Add cpuidle and power domains wake-up latency figures for OMAP3, cf.
> comments in the code and [1] for the details on where the numbers
> are magically coming from
> . Implement the relation between the cpuidle and per-device PM QoS frameworks
> in the OMAP3 specific idle callbacks.
> The chosen C-state shall satisfy the following conditions:
> . the 'valid' field is enabled,
> . it satisfies the enable_off_mode flag,
> . the next state for MPU and CORE power domains is not lower than the
> state programmed by the per-device PM QoS.
I had a couple minor comments on this version, but after that, feel free
to add:
Reviewed-by: Kevin Hilman <khilman@ti.com>
after that, this series will go upstream through Paul.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/6] PM QoS: implement the OMAP low level constraints management code
Date: Tue, 13 Dec 2011 15:53:20 -0800 [thread overview]
Message-ID: <87zkewrpu7.fsf@ti.com> (raw)
In-Reply-To: <1323706701-6627-1-git-send-email-j-pihet@ti.com> (jean pihet's message of "Mon, 12 Dec 2011 17:18:15 +0100")
Hi Jean,
jean.pihet at newoldbits.com writes:
> From: Jean Pihet <j-pihet@ti.com>
>
> . Implement the devices wake-up latency constraints using the global
> device PM QoS notification handler which applies the constraints to the
> underlying layer
> . Implement the low level code which controls the power domains next power
> states, through the hwmod and pwrdm layers
> . Add cpuidle and power domains wake-up latency figures for OMAP3, cf.
> comments in the code and [1] for the details on where the numbers
> are magically coming from
> . Implement the relation between the cpuidle and per-device PM QoS frameworks
> in the OMAP3 specific idle callbacks.
> The chosen C-state shall satisfy the following conditions:
> . the 'valid' field is enabled,
> . it satisfies the enable_off_mode flag,
> . the next state for MPU and CORE power domains is not lower than the
> state programmed by the per-device PM QoS.
I had a couple minor comments on this version, but after that, feel free
to add:
Reviewed-by: Kevin Hilman <khilman@ti.com>
after that, this series will go upstream through Paul.
Kevin
next prev parent reply other threads:[~2011-12-13 23:53 UTC|newest]
Thread overview: 29+ 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 at newoldbits.com
2011-12-12 16:18 ` jean.pihet
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
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 ` Kevin Hilman [this message]
2011-12-13 23:53 ` [PATCH v5 0/6] PM QoS: implement the OMAP low level constraints management code 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-12 16:18 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=87zkewrpu7.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.