Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Anand Moon <linux.amoon@gmail.com>,
	Daniel Lezcano <daniel.lezcano@free.fr>
Cc: "Krzysztof Kozłowski" <k.kozlowski@samsung.com>,
	"Kukjin Kim" <kgene@kernel.org>,
	"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>
Subject: Re: CPUIdle for Exynos5422 Odroid-XU3/XU4 boards.
Date: Thu, 20 Aug 2015 20:50:46 +0200	[thread overview]
Message-ID: <55D62186.1080002@linaro.org> (raw)
In-Reply-To: <CANAwSgRHEXuNt1PJY89ujificXj70BhbGhSOpL16yKsKr6hWcQ@mail.gmail.com>

On 08/20/2015 08:15 PM, Anand Moon wrote:
> Hi Daniel,
>
> On 20 August 2015 at 21:40, Daniel Lezcano <daniel.lezcano@free.fr> wrote:
>> On 08/20/2015 12:54 PM, Anand Moon wrote:
>>>
>>> Hello Krzysztof/Kukjim,
>>>
>>> CPUIdle seen to be not working for Exynos5422 Odroid boards.
>>>
>>> Is their any way this feature will be implemented in the future.
>>
>>
>> Yeah a good willing to fix the bl1. More than one year asking for that !
>> nooo way !!
>>
>> Your answer is at the end of
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-June/350632.html
>>
>>
>
> Thanks for the explanation.
>
> I was just referring following the source code.
>
> https://github.com/hardkernel/linux/blob/odroidxu3-3.10.y/arch/arm/mach-exynos/cpuidle-exynos5422.c

Ah, thanks for the pointer. So for my information, is that driver not 
working with the exynos5422 ?

> It seem that cpufreq and cpuidle go hand in hand.

At the first glance, there is a dependency with the cluster power state. 
It is not allowed to enter the cluster power down if another subsystem 
deny it. The driver itself is a pack of hacks based on cpuidle legacy 
code and wildly backported from older kernels with arbitrary latency and 
residency values.


-- 
  <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

  reply	other threads:[~2015-08-20 18:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 10:54 CPUIdle for Exynos5422 Odroid-XU3/XU4 boards Anand Moon
2015-08-20 16:10 ` Daniel Lezcano
2015-08-20 18:15   ` Anand Moon
2015-08-20 18:50     ` Daniel Lezcano [this message]
2015-08-21  0:55     ` Krzysztof Kozlowski
2015-08-21  3:41       ` Anand Moon
2015-08-21  3:59         ` Krzysztof Kozlowski
2015-08-21  7:21           ` Javier Martinez Canillas
2015-08-23  1:26             ` Krzysztof Kozlowski
2015-08-25  9:43               ` Javier Martinez Canillas
2015-08-25 14:35                 ` Bartlomiej Zolnierkiewicz
2015-08-25 16:09                   ` Lorenzo Pieralisi
2015-08-27 16:58                     ` Bartlomiej Zolnierkiewicz
2015-08-28  8:35                       ` Javier Martinez Canillas
2015-08-28 12:42                         ` Krzysztof Kozlowski
2015-08-28 12:50                           ` Bartlomiej Zolnierkiewicz
2015-10-12 19:06                           ` Amit Kucheria
2015-08-24  7:06             ` Przemyslaw Marczak

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=55D62186.1080002@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=daniel.lezcano@free.fr \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux.amoon@gmail.com \
    /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