amit daniel kachhap wrote:
>
> On Sat, Aug 10, 2013 at 12:14 PM, Viresh Kumar
> wrote:
> > Most of the CPUFreq drivers do similar things in .exit() and .verify()
> routines
> > and .attr. So its better if we have generic routines for them which can
> be used
> > by cpufreq drivers then.
> >
> >
On Sat, Aug 10, 2013 at 12:14 PM, Viresh Kumar wrote:
> Most of the CPUFreq drivers do similar things in .exit() and .verify()
> routines
> and .attr. So its better if we have generic routines for them which can be
> used
> by cpufreq drivers then.
>
> This patch uses these generic routines for
amit daniel kachhap wrote:
On Sat, Aug 10, 2013 at 12:14 PM, Viresh Kumar viresh.ku...@linaro.org
wrote:
Most of the CPUFreq drivers do similar things in .exit() and .verify()
routines
and .attr. So its better if we have generic routines for them which can
be used
by cpufreq drivers
On Sat, Aug 10, 2013 at 12:14 PM, Viresh Kumar viresh.ku...@linaro.org wrote:
Most of the CPUFreq drivers do similar things in .exit() and .verify()
routines
and .attr. So its better if we have generic routines for them which can be
used
by cpufreq drivers then.
This patch uses these
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Kukjin Kim
Signed-off-by: Viresh Kumar
---
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by:
6 matches
Mail list logo