On Fri, May 2, 2014 at 12:22 AM, Viresh Kumar wrote:
> On 2 May 2014 10:48, Nishanth Menon wrote:
>> On Thu, May 1, 2014 at 11:30 PM, Viresh Kumar
>> wrote:
diff --git a/drivers/cpufreq/cpufreq_opp.c b/drivers/cpufreq/cpufreq_opp.c
new file mode 100644
index 000..2602ff8
On 2 May 2014 10:48, Nishanth Menon wrote:
> On Thu, May 1, 2014 at 11:30 PM, Viresh Kumar wrote:
>>> diff --git a/drivers/cpufreq/cpufreq_opp.c b/drivers/cpufreq/cpufreq_opp.c
>>> new file mode 100644
>>> index 000..2602ff8
>>> --- /dev/null
>>> +++ b/drivers/cpufreq/cpufreq_opp.c
>>> @@ -0,
On Thu, May 1, 2014 at 11:30 PM, Viresh Kumar wrote:
> On 2 May 2014 06:36, Nishanth Menon wrote:
>> diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig
>> index 1fbe11f..281ccfb 100644
>> --- a/drivers/cpufreq/Kconfig
>> +++ b/drivers/cpufreq/Kconfig
>> @@ -17,6 +17,11 @@ config CPU_F
On 2 May 2014 06:36, Nishanth Menon wrote:
> diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig
> index 1fbe11f..281ccfb 100644
> --- a/drivers/cpufreq/Kconfig
> +++ b/drivers/cpufreq/Kconfig
> @@ -17,6 +17,11 @@ config CPU_FREQ
>
> if CPU_FREQ
>
> +config CPU_FREQ_PM_OPP
> + bo
CPUFREQ specific functions for OPP (Operating Performance Points) can
be isolated to just cpufreq. This allows for independent modifications
as needed. The functionality desired by cpufreq can easily be provided
by existing functions and any future "special handling" needed for
cpufreq drivers can
