diff options
| author | Ionela Voinescu <[email protected]> | 2020-12-14 12:38:20 +0000 |
|---|---|---|
| committer | Rafael J. Wysocki <[email protected]> | 2020-12-15 19:19:31 +0100 |
| commit | d2641a5c3d5ecaa1078225e493c7fed821715a04 (patch) | |
| tree | ed7c39a5f4f0e9004792203956d72d267d18d52d /lib/test_fortify/write_overflow-strcpy.c | |
| parent | defa0c6b94db6156c0e2c97e4cedf7986b24730a (diff) | |
cppc_cpufreq: use policy->cpu as driver of frequency setting
Considering only the currently supported coordination types (ANY, HW,
NONE), this change only makes a difference for the ANY type, when
policy->cpu is hotplugged out. In that case the new policy->cpu will
be different from ((struct cppc_cpudata *)policy->driver_data)->cpu.
While in this case the controls of *ANY* CPU could be used to drive
frequency changes, it's more consistent to use policy->cpu as the
leading CPU, as used in all other cppc_cpufreq functions. Additionally,
the debug prints in cppc_set_perf() would no longer create confusion
when referring to a CPU that is hotplugged out.
Signed-off-by: Ionela Voinescu <[email protected]>
Acked-by: Viresh Kumar <[email protected]>
Tested-by: Mian Yousaf Kaukab <[email protected]>
Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strcpy.c')
0 files changed, 0 insertions, 0 deletions