From: jon-hunter@ti.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 8/8] ARM: OMAP2+: PMU: Add QoS constraint
Date: Mon, 24 Sep 2012 11:08:29 -0500 [thread overview]
Message-ID: <5060857D.5030005@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1209201705570.12583@utopia.booyaka.com>
Hi Paul,
On 09/20/2012 12:14 PM, Paul Walmsley wrote:
> Hi
>
> On Mon, 10 Sep 2012, Jon Hunter wrote:
>
>> When CPU-idle is enabled, the MPU sub-system will transition to low power
>> states during idle periods. If the PMU is active and the MPU sub-system
>> transitions to a low power state, such as retention, then the PMU context
>> will be lost and PMU events will stop. To prevent this from happening add a
>> QoS constraint whenever PMU is active to prevent the MPU sub-system from
>> transitioning to a low power state.
>>
>> By default the PMU QoS constraint is set to -1 so it will not prevent any low
>> power states and when the PMU is enabled, it is set to 0, so that only C-state
>> C0 is allowed. I plan to re-visit this and relax the constraint to allow some
>> low power states, but for now I just wish to ensure PMU is working.
>>
>> Cc: Ming Lei <ming.lei@canonical.com>
>> Cc: Will Deacon <will.deacon@arm.com>
>> Cc: Benoit Cousson <b-cousson@ti.com>
>> Cc: Paul Walmsley <paul@pwsan.com>
>> Cc: Kevin Hilman <khilman@ti.com>
>>
>> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
>
> This one looks like 3.7-rc material, due to the dependency on Will's PMU
> runtime PM adaptation series, which is unfortunately not yet in the
> stable merge base that I need to use to send these upstream. Jon, care to
> update and re-send this one after Linus merges the other PMU patches?
Yes no problem. Will send out during the 3.7-rc.
Cheers
Jon
next prev parent reply other threads:[~2012-09-24 16:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 15:23 [PATCH V3 0/8] ARM: OMAP4: Add PMU Support Jon Hunter
2012-09-10 15:23 ` [PATCH V3 1/8] ARM: OMAP3: Add debugss HWMOD data Jon Hunter
2012-09-13 3:32 ` Jon Hunter
2012-09-19 17:34 ` Paul Walmsley
2012-09-20 17:13 ` Paul Walmsley
2012-09-24 15:57 ` Jon Hunter
2012-09-10 15:23 ` [PATCH V3 2/8] ARM: OMAP2+: PMU: Convert OMAP2/3 devices to use HWMOD Jon Hunter
2012-09-10 15:23 ` [PATCH V3 3/8] ARM: OMAP4: Re-map the CTIs IRQs from MPU to DEBUGSS Jon Hunter
2012-09-20 17:00 ` Paul Walmsley
2012-09-10 15:23 ` [PATCH V3 4/8] ARM: OMAP4430: Create PMU device via HWMOD Jon Hunter
2012-09-20 17:14 ` Paul Walmsley
2012-09-10 15:23 ` [PATCH V3 5/8] ARM: OMAP2+: PMU: Add runtime PM support Jon Hunter
2012-09-10 15:23 ` [PATCH V3 6/8] ARM: OMAP4: Route PMU IRQs to CTI IRQs Jon Hunter
2012-09-20 16:59 ` Paul Walmsley
2012-09-24 19:46 ` Jon Hunter
2012-09-10 15:23 ` [PATCH V3 7/8] ARM: OMAP4: Enable PMU for OMAP4460/70 Jon Hunter
2012-09-10 15:23 ` [PATCH V3 8/8] ARM: OMAP2+: PMU: Add QoS constraint Jon Hunter
2012-09-20 17:14 ` Paul Walmsley
2012-09-24 16:08 ` Jon Hunter [this message]
2012-09-11 6:48 ` [PATCH V3 0/8] ARM: OMAP4: Add PMU Support Shilimkar, Santosh
2012-09-20 17:17 ` Paul Walmsley
2012-09-20 17:39 ` Shilimkar, Santosh
2012-09-20 17:43 ` Paul Walmsley
2012-09-20 17:52 ` Shilimkar, Santosh
2012-09-20 21:09 ` Will Deacon
2012-09-24 21:45 ` Jon Hunter
2012-10-01 9:45 ` Will Deacon
2012-10-01 15:03 ` Jon Hunter
2012-09-24 21:43 ` Jon Hunter
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=5060857D.5030005@ti.com \
--to=jon-hunter@ti.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).