diff options
author | Dave Jones <davej@redhat.com> | 2006-03-05 03:35:00 -0500 |
---|---|---|
committer | Dave Jones <davej@redhat.com> | 2006-03-05 03:35:00 -0500 |
commit | 2a1c1c877ecb446dbdf1715248e151db8719a87b (patch) | |
tree | d265e90cdbcbfc9b76a1c183a03688eddb5d0e6f /drivers/cpufreq | |
parent | 32ee8c3e470d86588b51dc42ed01e85c5fa0f180 (diff) |
[CPUFREQ] powernow-k8: Let cpufreq driver handle affected CPUs
powernow-k8: Let cpufreq driver handle affected CPUs
Let the cpufreq driver manage AMD Dual-Core CPUs being tied together.
Since cpufreq driver's affected CPUs data, cpufreq_policy->cpus, already
knows about which cores are tied together, powernow driver does not have
keep its internal data for every core. (even a pointer.. it will never
be called on) Telling cpufreq driver about cpu_core_map at init time is
sufficient.
Signed-off-by: Jacob Shin <jacob.shin@amd.com>
Signed-off-by: Dave Jones <davej@redhat.com>
Diffstat (limited to 'drivers/cpufreq')
0 files changed, 0 insertions, 0 deletions