On Thursday, September 12, 2013 11:06:14 AM Viresh Kumar wrote: > On 12 September 2013 06:13, Rafael J. Wysocki > <rafael.j.wysocki@xxxxxxxxx> wrote: > > Yes, if you can point to a specific driver having this problem. > > There are so many of those (I know it because I went through almost all drivers > recently with my cleanup series): cpufreq-cpu0, omap-cpufreq, > exynos-cpufreq, etc.. > > They all do this: > > A. If new freq is more than old: Increase voltage > B. Change freq > C. If new freq is less than old: decrease voltage Well, if there's more than one it's even simpler. You can just pick one. :-) Like, "for example, <driver name> does the following ... which may cause the hardware to misbehave, because ...". Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
