On 27 November 2013 01:51, Rafael J. Wysocki rjw@rjwysocki.net wrote:
I was talking about the case when your
__cpufreq_driver_target(policy, policy->cur - 1, CPUFREQ_RELATION_L);
fails. The other case is not really interesting.
Okay.. I actually thought the context of this chat is about "not fixing the frequency silently". That's what Dirk pointed out, if I am not wrong.
And hence I also support the new pr_warn I have added in those cases. But yes a WARN_ON() can be printed out in case __cpufreq_driver_target() fails.