CPUIdle Armada 370
gregory.clement at free-electrons.com
Wed Aug 6 08:28:33 PDT 2014
On 06/08/2014 17:14, Gregory CLEMENT wrote:
> Hi Nicolas,
> On 06/08/2014 16:01, Nicolas Derouineau wrote:
>> I am currently trying to use the CPUIdle driver provided by linux-next (or by the patch here https://github.com/MISL-EBU-System-SW/mainline-public/commits/3.16/cpuidle-v3).
> I have just tested using next-20140806 and mvebu_v7_defconfig.
> And it worked well on a mirabox using the Armada 370 SoC.
>> Everything runs fine as long as I don't select the CPU driver for the ARMADA Family. When I do, at boottime, the program is entering the __cpu_suspend save function and then get lost in it and that turns into a kernel panic. I have already made a post about this on the ARM Community Forum (http://community.arm.com/thread/6326).
>> The "faulty" configuration file is attached to this email.
> Now I will try with this configuration
Using your configuration file I didn't reproduce your issue.
And according to the stat given by linux the kernel spent a lot
of time in idle:
Could you try again with next-20140806?
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
More information about the linux-arm-kernel