From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Russell King <linux@arm.linux.org.uk>,
Kukjin Kim <kgene.kim@samsung.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Sachin Kamat <sachin.kamat@samsung.com>,
Tushar Behera <tushar.behera@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org,
Kyungmin Park <kyungmin.park@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Tomasz Figa <t.figa@samsung.com>
Subject: Re: [PATCH 1/3] cpuidle: exynos: Allow to use the driver without AFTR
Date: Mon, 21 Jul 2014 12:08:45 +0200 [thread overview]
Message-ID: <1405937325.21645.2.camel@AMDC1943> (raw)
In-Reply-To: <53CCE31C.90300@linaro.org>
On pon, 2014-07-21 at 11:53 +0200, Daniel Lezcano wrote:
> On 07/21/2014 10:36 AM, Krzysztof Kozlowski wrote:
> > Allow the driver to be used when AFTR enter function is not provided
> > (device platform data is NULL).
> >
> > This actually does not give any special energy-saving benefits but
> > allows to track the idle time of each core. Additionally it is a safe
> > way to validate supplied platform data.
> >
> > Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>
> I think we already talk about this in the mailing list several times.
> It does not make sense to enable the cpuidle driver for WFI just for the
> sake of tracking via sysfs some idle timings.
>
> Using the cpuidle driver means using the underlying cpuidle
> infrastructure with all the stats computation in the governor.
>
> If there is a *real* need of a WFI cpuidle driver, then a generic WFI
> cpuidle driver could be implemented to supersede this one.
>
> It took a while to cleanup this driver and remove all the hacks around
> this AFTR state... :)
Sure, I understand.
Best regards,
Krzysztof
>
> > ---
> > drivers/cpuidle/cpuidle-exynos.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/cpuidle/cpuidle-exynos.c b/drivers/cpuidle/cpuidle-exynos.c
> > index 7c0151263828..5325a394be7e 100644
> > --- a/drivers/cpuidle/cpuidle-exynos.c
> > +++ b/drivers/cpuidle/cpuidle-exynos.c
> > @@ -77,7 +77,10 @@ static int exynos_cpuidle_probe(struct platform_device *pdev)
> > {
> > int ret;
> >
> > + /* If NULL enter only WFI */
> > exynos_enter_aftr = (void *)(pdev->dev.platform_data);
> > + if (!exynos_enter_aftr)
> > + exynos_idle_driver.state_count = 1;
> >
> > ret = cpuidle_register(&exynos_idle_driver, NULL);
> > if (ret) {
> >
>
>
prev parent reply other threads:[~2014-07-21 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 8:36 [PATCH 1/3] cpuidle: exynos: Allow to use the driver without AFTR Krzysztof Kozlowski
2014-07-21 8:36 ` [PATCH 2/3] ARM: EXYNOS: Enable cpuidle in WFI on all SoCs Krzysztof Kozlowski
2014-07-21 8:36 ` [PATCH 3/3] ARM: exynos_defconfig: Enable cpuidle driver Krzysztof Kozlowski
2014-07-21 9:53 ` [PATCH 1/3] cpuidle: exynos: Allow to use the driver without AFTR Daniel Lezcano
2014-07-21 10:08 ` 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=1405937325.21645.2.camel@AMDC1943 \
--to=k.kozlowski@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=rjw@rjwysocki.net \
--cc=sachin.kamat@samsung.com \
--cc=t.figa@samsung.com \
--cc=tushar.behera@linaro.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).