diff options
author | Gautham R. Shenoy <ego@linux.vnet.ibm.com> | 2014-04-01 11:13:27 +0400 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2014-04-07 16:35:28 +0400 |
commit | 0692c69138355fdbf32ecf70a2cde9c1fc3d7bb2 (patch) | |
tree | ef6725bf8c0868795a8e8583953684cfc76d95af /drivers/cpufreq/ia64-acpi-cpufreq.c | |
parent | b3d627a5f2bf1a9a486f65af6f7c2ce0e09b3d12 (diff) | |
download | linux-0692c69138355fdbf32ecf70a2cde9c1fc3d7bb2.tar.xz |
cpufreq: powernv: Use cpufreq_frequency_table.driver_data to store pstate ids
The .driver_data field in the cpufreq_frequency_table was supposed to
be private to the drivers. However at some later point, it was being
used to indicate if the particular frequency in the table is the
BOOST_FREQUENCY. After patches [1] and [2], the .driver_data is once
again private to the driver. Thus we can safely use
cpufreq_frequency_table.driver_data to store pstate_ids instead of
having to maintain a separate array powernv_pstate_ids[] for this
purpose.
[1]:
Subject: cpufreq: don't print value of .driver_data from core
From : Viresh Kumar <viresh.kumar@ linaro.org>
url : http://marc.info/?l=linux-pm&m=139601421504709&w=2
[2]:
Subject: cpufreq: create another field .flags in cpufreq_frequency_table
From : Viresh Kumar <viresh.kumar@linaro.org>
url : http://marc.info/?l=linux-pm&m=139601416804702&w=2
Signed-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/ia64-acpi-cpufreq.c')
0 files changed, 0 insertions, 0 deletions