From: Daniel Lezcano <daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Peter De Schrijver
<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "rjw-KKrjLPT3xs0@public.gmane.org"
<rjw-KKrjLPT3xs0@public.gmane.org>,
"linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org"
<linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org>,
"patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 0/4][V2] cpuidle : multiple drivers support
Date: Thu, 25 Oct 2012 16:11:32 +0200 [thread overview]
Message-ID: <50894894.7050609@linaro.org> (raw)
In-Reply-To: <20121025134933.GA1962-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
On 10/25/2012 03:49 PM, Peter De Schrijver wrote:
> On Fri, Oct 19, 2012 at 12:10:45PM +0200, Daniel Lezcano wrote:
>> The discussion about having different cpus on the system with
>> different latencies bring us to a first attemp by adding a
>> pointer in the cpuidle_device to the states array.
>>
>> But as Rafael suggested, it would make more sense to create a
>> driver per cpu [1].
>>
>> This patch adds support for multiple cpuidle drivers.
>>
>> It creates a per cpu cpuidle driver pointer.
>>
>> In order to not break the different drivers, the function cpuidle_register_driver
>> assign for each cpu, the driver.
>>
>> The multiple driver support is optional and if it is not set, the cpuide driver
>> core code remains the same (except some code reorganisation).
>>
>> I did the following tests compiled, booted, tested without/with CONFIG_CPU_IDLE,
>> with/without CONFIG_CPU_IDLE_MULTIPLE_DRIVERS.
>>
>> Tested on Core2 Duo T9500 with acpi_idle [and intel_idle]
>> Tested on ARM Dual Cortex-A9 U8500 (aka Snowball)
>>
>> V1 tested on Tegra3 and Vexpress TC2
>>
>
> V2 tested on Tegra3.
Cool thanks !
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
next prev parent reply other threads:[~2012-10-25 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1350641449-22863-1-git-send-email-daniel.lezcano@linaro.org>
2012-10-25 13:49 ` [PATCH 0/4][V2] cpuidle : multiple drivers support Peter De Schrijver
[not found] ` <20121025134933.GA1962-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2012-10-25 14:11 ` Daniel Lezcano [this message]
2012-10-25 20:29 ` Rafael J. Wysocki
[not found] ` <4190590.cE8oL2xMlM-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2012-10-26 8:23 ` Peter De Schrijver
2012-10-26 19:23 ` Daniel Lezcano
2012-10-26 21:10 ` Rafael J. Wysocki
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=50894894.7050609@linaro.org \
--to=daniel.lezcano-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=rjw-KKrjLPT3xs0@public.gmane.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 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.