From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Exynos4: cpuidle: support dual CPUs with AFTR state
Date: Wed, 25 Jun 2014 09:36:40 +0200 [thread overview]
Message-ID: <1403681800.19087.8.camel@AMDC1943> (raw)
In-Reply-To: <539B7E74.7000605@linaro.org>
On sob, 2014-06-14 at 00:43 +0200, Daniel Lezcano wrote:
> On 06/11/2014 10:50 AM, Krzysztof Kozlowski wrote:
(...)
> >
> > Hi,
> >
> > Shouldn't the exynos_idle_barrier be initialized here?
>
> As it is a static data it will be initialized to zero.
>
> > I know you sent the patch almost 2 months ago but I stomped on this
> > while testing it on Exynos3250.
>
> No problem. And what results on exynos3250 ?
I had to change some of the ways for synchronization two cores (boot
vector behaves differently) so actually the driver is different except
the general idea. As for the results (on dual-core Exynos3250) - the
mode (AFTR+CPU1 off) consumes about 5% less energy than idle-WFI state.
I expect there will be much more savings in deeper mode (called here
W-AFTR).
Best regards,
Krzysztof
prev parent reply other threads:[~2014-06-25 7:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 9:48 [PATCH] Exynos4: cpuidle: support dual CPUs with AFTR state Daniel Lezcano
2014-04-04 14:25 ` Lorenzo Pieralisi
2014-04-15 6:37 ` Lukasz Majewski
2014-04-15 15:23 ` Daniel Lezcano
2014-04-15 15:54 ` Lukasz Majewski
2014-04-15 16:38 ` Daniel Lezcano
2014-04-15 22:19 ` Lukasz Majewski
2014-04-24 17:42 ` Tomasz Figa
2014-04-25 7:52 ` Daniel Lezcano
2014-05-30 9:30 ` Daniel Lezcano
2014-05-30 11:34 ` Tomasz Figa
2014-05-30 13:53 ` Bartlomiej Zolnierkiewicz
2014-07-16 17:34 ` Bartlomiej Zolnierkiewicz
2014-07-21 11:06 ` Daniel Lezcano
2014-08-14 10:55 ` Bartlomiej Zolnierkiewicz
2014-08-14 23:57 ` Daniel Lezcano
2014-06-11 8:50 ` Krzysztof Kozlowski
2014-06-13 22:43 ` Daniel Lezcano
2014-06-25 7:36 ` Krzysztof Kozlowski [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=1403681800.19087.8.camel@AMDC1943 \
--to=k.kozlowski@samsung.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).