From: santosh.shilimkar@ti.com (Santosh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] CPU PM notifiers
Date: Fri, 16 Sep 2011 10:20:27 +0530 [thread overview]
Message-ID: <4E72D593.9020902@ti.com> (raw)
In-Reply-To: <1315060755-4613-1-git-send-email-santosh.shilimkar@ti.com>
On Saturday 03 September 2011 08:09 PM, Santosh Shilimkar wrote:
> Updates V2:
> - The CPU PM notifiers are moved to generic level instead of keeping
> it ARM specific as per Rafael's comment.
> - To avoid every driver duplicating the sys-core ops and cpu pm notfiers,
> the CPU PM common notifier is registering it in one place so that
> suspend is taken care.
> - CPU COMPLEX events are renamed to more appropriate CPU CLUSTER.
> - GIC distributor is not disabled to avoid the live locks. This is
> observed with CPUIDLE cases where at time CPU cluster fails to
> transition to low power states. As such there was no need to
> disable distributor in first place since on cluster reset, it
> will get disabled anyways.
> - In VFP code, syscore ops are dropped in favour of CPU PM
> notifiers since S2R is already handled in core CPU PM notifiers.
> - The last patch is an independent patch but can be pushed along with
> the other GIC changes done here.
>
> V1: [http://lwn.net/Articles/447259/]
>
> This patch set tries to address concerns with platform pm code
> calling into the driver for every block in the Cortex A9s
> during idle, hotplug, and suspend. The first patch adds cpu pm
> notifiers that can be called by platform code, the second uses
> the notifier to save and restore the GIC state, and the third
> saves the VFP state.
>
> The notifiers are used for two types of events, CPU PM events and
> CPU cluster PM events. CPU PM events are used to save and restore
> per-cpu context when a single CPU is preparing to enter or has
> just exited a low power state. For example, the VFP saves the
> last thread context, and the GIC saves banked CPU registers.
>
> CPU cluster events are used after all the CPUs in a power domain
> have been prepared for the low power state. The GIC uses these
> events to save global register state.
>
> L2 cache is not covered by this patch set, as the determination
> of when the L2 is reset and when it is retained is
> platform-specific, and most of the APIs necessary are already
>
>
> The series is tested with OMAP4 with S2R and CPUIDLE.
>
> The following changes since commit c6a389f123b9f68d605bb7e0f9b32ec1e3e14132:
>
> Linux 3.1-rc4 (2011-08-28 21:16:01 -0700)
>
> Colin Cross (5):
> cpu_pm: Add cpu power management notifiers
> cpu_pm: call notifiers during suspend
> ARM: gic: Use cpu pm notifiers to save gic state
> ARM: vfp: Use cpu pm notifiers to save vfp state
> ARM: gic: Allow gic arch extensions to provide irqchip flags
>
Thanks all for the reviews and testing of this series.
I am going to add these patches as part of my pull request
to Russell for the 3.2.
Regards
Santosh
prev parent reply other threads:[~2011-09-16 4:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-03 14:39 [PATCH v2 0/5] CPU PM notifiers Santosh Shilimkar
2011-09-03 14:39 ` [PATCH v2 1/5] cpu_pm: Add cpu power management notifiers Santosh Shilimkar
2011-09-09 22:56 ` Andrew Morton
2011-09-10 4:02 ` Santosh
2011-09-10 9:31 ` Santosh
2011-09-12 5:02 ` Santosh
2011-09-13 5:42 ` Santosh
2011-09-03 14:39 ` [PATCH v2 2/5] cpu_pm: call notifiers during suspend Santosh Shilimkar
2011-09-07 20:02 ` Kevin Hilman
2011-09-08 5:16 ` Santosh
2011-09-08 14:01 ` Kevin Hilman
2011-09-08 16:12 ` Santosh
2011-09-08 17:56 ` Kevin Hilman
2011-09-08 18:04 ` Colin Cross
2011-09-08 20:51 ` Kevin Hilman
2011-09-09 6:27 ` Santosh
2011-09-03 14:39 ` [PATCH v2 3/5] ARM: gic: Use cpu pm notifiers to save gic state Santosh Shilimkar
2011-09-03 14:39 ` [PATCH v2 4/5] ARM: vfp: Use cpu pm notifiers to save vfp state Santosh Shilimkar
2011-09-03 14:39 ` [PATCH v2 5/5] ARM: gic: Allow gic arch extensions to provide irqchip flags Santosh Shilimkar
2011-09-06 2:34 ` [PATCH v2 0/5] CPU PM notifiers Shawn Guo
2011-09-06 5:17 ` Santosh
2011-09-09 18:00 ` Kevin Hilman
2011-09-10 5:53 ` Santosh
2011-09-16 4:50 ` Santosh [this message]
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=4E72D593.9020902@ti.com \
--to=santosh.shilimkar@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).