On 21.08.2015 12:41, Anand Moon wrote:
> Hi Krzysztof,
> 
> On 21 August 2015 at 06:25, Krzysztof Kozlowski <k.kozlow...@samsung.com> 
> wrote:
>> On 21.08.2015 03:15, Anand Moon wrote:
>>> Hi Daniel,
>>>
>>> On 20 August 2015 at 21:40, Daniel Lezcano <daniel.lezc...@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
>>>
>>> It seem that cpufreq and cpuidle go hand in hand.
>>
>> Bartlomiej was working on cpufreq for Exynos542x:
>> http://lkml.iu.edu/hypermail/linux/kernel/1504.2/03139.html
>>
>> It would be nice to have also cpuidle and suspend features working on
>> Exynos542x family but this depends on firmware. Some time ago I
>> struggled with suspend on Arndale Octa (Exynos5420) and I failed. I
>> think the firmware is the issue here.
>>
>> Actually I am not sure what is your question Anand. You are asking if
>> someone plans to do this?
> 
> Yes I am asking are their plans to implement cpufreq and cpuidle 
> simultaneously.

There are no obstacles for implementing them simultaneously so the
question is rather who plans to do the cpuidle driver for Exynos542x? I
don't... at least in nearby future. If I had some spare time then
probably I would try to make suspend working.

Best regards,
Krzysztof

--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to