From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/5] coupled cpuidle state support
Date: Fri, 30 Mar 2012 18:23:30 +0530 [thread overview]
Message-ID: <4F75ACCA.4090009@ti.com> (raw)
In-Reply-To: <CAMbhsRQAw2+as13NVvWkh7ojyRs+jNpFist2gmiiEY52U=o84A@mail.gmail.com>
Colin,
On Friday 16 March 2012 05:07 AM, Colin Cross wrote:
> On Wed, Mar 14, 2012 at 11:29 AM, Colin Cross <ccross@android.com> wrote:
[...]
>>
>> v2:
>> * removed the coupled lock, replacing it with atomic counters
>> * added a check for outstanding pokes before beginning the
>> final transition to avoid extra wakeups
>> * made the cpuidle_coupled struct completely private
>> * fixed kerneldoc comment formatting
>> * added a patch with a helper function for resynchronizing
>> cpus after aborting idle
>> * added a patch (not for merging) to add trace events for
>> verification and performance testing
>
> I forgot to mention, this patch series is on v3.3-rc7, and will
> conflict with the cpuidle timekeeping patches. If those go in first
> (which is likely), I will rework this series on top of it. I left it
> on v3.3-rc7 now to make testing easier.
I have re-based your series against Len Browns
next branch [1] which has time keeping and other cpuidle patches.
Have also folded the CPU hotplug fix which I posted in the
original coupled idle patch.
If you want, the updated branch can be pulled from:
git://gitorious.org/omap-sw-develoment/linux-omap-dev.git
for_3.5/coupled_cpuidle-rebase
Regards
Santosh
[1] Power Management
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux.git
next prev parent reply other threads:[~2012-03-30 12:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 18:29 [PATCHv2 0/5] coupled cpuidle state support Colin Cross
2012-03-14 18:29 ` [PATCHv2 1/5] cpuidle: refactor out cpuidle_enter_state Colin Cross
2012-03-14 18:29 ` [PATCHv2 2/5] cpuidle: fix error handling in __cpuidle_register_device Colin Cross
2012-03-14 18:29 ` [PATCHv2 3/5] cpuidle: add support for states that affect multiple cpus Colin Cross
2012-03-16 0:04 ` Kevin Hilman
2012-03-16 0:20 ` Colin Cross
2012-03-16 1:52 ` Arjan van de Ven
2012-03-17 12:29 ` Santosh Shilimkar
2012-03-17 19:21 ` Colin Cross
2012-03-18 7:18 ` Shilimkar, Santosh
2012-03-14 18:29 ` [PATCHv2 4/5] cpuidle: coupled: add parallel barrier function Colin Cross
2012-03-14 18:29 ` [PATCHv2 5/5] cpuidle: coupled: add trace events Colin Cross
2012-04-09 6:59 ` Santosh Shilimkar
2012-03-15 23:37 ` [PATCHv2 0/5] coupled cpuidle state support Colin Cross
2012-03-30 12:53 ` Santosh Shilimkar [this message]
2012-04-09 7:11 ` Santosh Shilimkar
2012-04-09 23:35 ` [linux-pm] " Kevin Hilman
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=4F75ACCA.4090009@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).