From: trinabh@linux.vnet.ibm.com (Trinabh Gupta)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH V5 0/4] cpuidle: global registration of idle states with per-cpu statistics
Date: Mon, 06 Jun 2011 19:09:18 +0530 [thread overview]
Message-ID: <20110606133917.5670.54949.stgit@tringupt.in.ibm.com> (raw)
The following patch series implements global registration of cpuidle
states, and also has the necessary data structure changes to
accommodate the per-cpu writable members of the cpuidle_states
structure.
Previous version of the series (V4) is at https://lkml.org/lkml/2011/4/28/312
This series applies on 3.0-rc1
Changes from previous version (V4):
1. Rebased the series to 3.0-rc1
2. Made same changes for Samsung exynos4 cpuidle driver registration
Tests done:
1. Compile tested for ARM using the following configs: da8xx_omapl_defconfig,
exynos4_defconfig, kirkwood_defconfig, omap2plus_defconfig.
2. Boot tested on x86 nehalem with multiple C-states for both intel_idle
and acpi_idle drivers.
Thanks
-Trinabh
next reply other threads:[~2011-06-06 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 13:39 Trinabh Gupta [this message]
2011-06-06 13:39 ` [RFC PATCH V5 1/4] cpuidle: Move dev->last_residency update to driver enter routine, remove dev->last_state Trinabh Gupta
2011-06-06 13:51 ` Russell King - ARM Linux
2011-06-06 13:39 ` [RFC PATCH V5 2/4] cpuidle: Remove CPUIDLE_FLAG_IGNORE and dev->prepare() Trinabh Gupta
2011-06-06 13:39 ` [RFC PATCH V5 3/4] cpuidle: Split cpuidle_state structure and move per-cpu statistics fields Trinabh Gupta
2011-06-06 13:39 ` [RFC PATCH V5 4/4] cpuidle: Single/Global registration of idle states Trinabh Gupta
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=20110606133917.5670.54949.stgit@tringupt.in.ibm.com \
--to=trinabh@linux.vnet.ibm.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