Re: [PATCH RESEND] cpufreq: Make sure target freq is within limits

2012-10-30 Thread Rafael J. Wysocki
On Friday, October 26, 2012 06:05:21 PM Viresh Kumar wrote: > __cpufreq_driver_target() must not pass target frequency beyond the limits of > current policy. > > Today most of cpufreq platform drivers are doing this check in their target > routines. Why not move it to __cpufreq_driver_target(). >

Re: [PATCH RESEND] cpufreq: Make sure target freq is within limits

2012-10-30 Thread Rafael J. Wysocki
On Friday, October 26, 2012 06:05:21 PM Viresh Kumar wrote: __cpufreq_driver_target() must not pass target frequency beyond the limits of current policy. Today most of cpufreq platform drivers are doing this check in their target routines. Why not move it to __cpufreq_driver_target().

[PATCH RESEND] cpufreq: Make sure target freq is within limits

2012-10-26 Thread Viresh Kumar
__cpufreq_driver_target() must not pass target frequency beyond the limits of current policy. Today most of cpufreq platform drivers are doing this check in their target routines. Why not move it to __cpufreq_driver_target(). Signed-off-by: Viresh Kumar --- Hi Rafael, Resend doesn't contain

[PATCH RESEND] cpufreq: Make sure target freq is within limits

2012-10-26 Thread Viresh Kumar
__cpufreq_driver_target() must not pass target frequency beyond the limits of current policy. Today most of cpufreq platform drivers are doing this check in their target routines. Why not move it to __cpufreq_driver_target(). Signed-off-by: Viresh Kumar viresh.ku...@linaro.org --- Hi Rafael,