On Fri, Aug 28, 2015 at 6:12 PM, Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx> wrote: > W dniu 28.08.2015 o 17:35, Javier Martinez Canillas pisze: >> >> Ok, I'll see if I can take a look what is needed to implement a Exynos542x CPUidle >> driver. I'm quite busy with other stuff right now but I should be less busy in a >> couple of weeks. > > The only useful users of Exynos542x cpuidle would be Chromebooks. > Probably the same goes with suspend to RAM. Non-mobile devices could > leave without it. > > In the same time cpuidle and S2R would require a significant amount of > work. Testing would have to be performed on Chromebooks. I have doubts > it would work on Odroid XU3. > > I dug into S2R issues on Odroid XU3 and after fixing trivial imprecise > abort I don't have clue. It just dies somewhere in firmware/bootloader. > Vendor code has a lot more stuff related to suspend and testing it > one-by-one whether it fixes the issue is frustrating. > > Do we really need cpuidle or S2R on Exynos542x/5800? Cpuidle support on Odroid-XU3 and Peach-Pi would be useful for general PM/scheduler work on big.LITTLE systems. On the Odroid, it has the additional benefit of allowing power measurements, which helps. Regards, Amit -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html