On 03-06-16, 19:05, Viresh Kumar wrote:
Later patches would make changes in cpufreq core, after which policy->freq_table may be reordered by cpufreq core and it wouldn't be safe anymore to use 'index' for any other local arrays.
To prepare for that, use policy->freq_table[index].driver_data for other driver specific usage of 'index'. The 'driver_data' fields are already set properly by the driver.
Cc: Shawn Guo shawn.guo@freescale.com Signed-off-by: Viresh Kumar viresh.kumar@linaro.org
drivers/cpufreq/imx6q-cpufreq.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
Fixing Shawn's id.