Viresh,
If I'm not mistaken, Steve's change for allowing changes to remote CPUs was limiting it to slow path and also limiting it to only CPUs within the same cluster.
Our CPU scaling code doesn't have any such relation. We can set the frequency of any CPU from any CPU. I think it'll be best to push this detail to the CPUfreq driver. Maybe we can have a flag where the CPUfreq driver says it wants to do remote CPU setting or not. And then we can let the driver do the filtering as they see fit.
Can you do that change please?
Thanks, Saravana P.S: I'm not subscribed to eas-dev. I'll figure that out soon.
On 01/23/2017 03:21 AM, Viresh Kumar wrote:
<I'm able to read your email, but it is getting garbled for some reason when I try to reply. Deleted it.>
-- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project