RFC OMAP4 cpuidle cleanup
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 7 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 7 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/7] OMAP4 cpuidle cleanup
Quoted 7 lines · Santosh
Quoted 4 lines · Daniel Lezcano
This patchset is a proposition to improve a bit the code. The changes are code cleanup and does not change the behavior of the driver itself.
Thanks. Will have a look at your series.
Cool, thanks.
Quoted 4 lines
Quoted 1 line
A couple a things call my intention. Why the cpuidle device is set for cpu0 only
Because the mainline code CPUIDLE is supported along with CPUhotplug. This is going to change though with Couple CPUIDLE and corresponding OMAP updates.
Ok, thanks for the information. I will look deeper. What happens to cpu1 when it is online and has nothing to do ?
Quoted 3 lines
Quoted 2 lines
and why the WFI is not used ?
I didn't get this question. Do you mean the generic WFI?
yes.
Quoted 2 lines
If yes, then, it's mainly because OMAP need additional custom barriers.
Ah, ok. I am not sure if it is possible but that may be cool if we can call cpu_do_idle instead with additional barrier.
Quoted 4 lines
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 5 lines
<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