On Tuesday 01 July 2014 12:32 PM, Viresh Kumar wrote: > Drivers supporting multiple clusters or multiple 'struct cpufreq_policy' > instances may need to keep per-policy data. If the core doesn't support them, > they might do it in the most unoptimized way: 'per-cpu' data. > > This patch adds another field in 'struct cpufreq_policy': 'driver_data'. It > isn't accessed by core and is for driver's internal use. > > Signed-off-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx> > --- > include/linux/cpufreq.h | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h > index ec4112d..d4b1108 100644 > --- a/include/linux/cpufreq.h > +++ b/include/linux/cpufreq.h > @@ -112,6 +112,9 @@ struct cpufreq_policy { > spinlock_t transition_lock; > wait_queue_head_t transition_wait; > struct task_struct *transition_task; /* Task which is doing the transition */ > + > + /* For cpufreq driver's internal use */ > + void *driver_data; > }; > Minor comment for consistency either maintain same commenting style for the above structure (description after the variable) or may be clean up the comments in another patch. Regards, Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html