Thread (27 messages) 27 messages, 4 authors, 2014-02-26

[PATCH] cpufreq: Set policy to non-NULL only after all hotplug online work is done

From: skannan at codeaurora.org <hidden>
Date: 2014-02-24 09:00:08
Also in: linux-arm-msm, linux-pm, lkml

Viresh Kumar wrote:
On 24 February 2014 14:17,  [off-list ref] wrote:
quoted
Sorry, not sure I understand what you mean.

I agree, wording in my commit text might be unclear. I'll fix it after
we
agree on the code fix. In the MSM case, each CPU has it's own policy.

I'm assuming your original complaint was about my confusing wording.
Maybe
that's not what you were pointing out?
In your case each CPU has a separate policy structure as they have
separately
controllable clocks. But you also said that CPU0 is setting CPU1's
governor to
NULL. I don't see that happening. Each CPU sets its own governor to NULL
on
init().
When I said "CPU0 is setting CPU1's governor to NULL", I meant
thread/context running in CPU0 is setting CPU1's governor as part of
CPU1's ONLINE notifier.

-Saravana

-- 
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help