On 08-10-15, 13:55, Jon Medhurst (Tixy) wrote: > Looking a bit more carefully, the reason your fix doesn't work is that > bL_cpufreq_get_rate returns the last requested rate for this CPU, > whereas target_rate/new_rate is the maximum rate requested by any CPU on > the cluster (which is what we want the hardware set to).
Sigh.. > So sounds like my alternative fix of checking the 'actual' frequency > immediately after setting it is probably the way forward, unless Sudeep > chimes in with additional info about the issue he was trying to address. Right. -- viresh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
