lkml.org 
[lkml]   [2014]   [Mar]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] cpufreq: create another field .flags in cpufreq_frequency_table
On Fri, Mar 28, 2014 at 02:23:20PM +0530, Viresh Kumar wrote:
> Currently cpufreq frequency table has two fields: frequency and driver_data.
> driver_data is only for driver's internal use and cpufreq core shouldn't use it
> at all. But with the introduction of BOOST frequencies, this assumption was
> broken and we started using it as a flag instead.
>
> There are two problems due to this:
> - It is against the description of this field, as driver's data is used by core
> now.
> - if drivers fill it with -3 for any frequency, then those frequencies are never
> considered by cpufreq core as it is exactly same as value of
> CPUFREQ_BOOST_FREQ, i.e. ~2.
>
> The best way to get this fixed is by creating another field flags which will be
> used for such flags. This patch does that. Along with that various drivers need
> modifications due to the change of struct cpufreq_frequency_table.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

Thanks for this patch. A minor comment below:

> diff --git a/drivers/cpufreq/exynos4x12-cpufreq.c b/drivers/cpufreq/exynos4x12-cpufreq.c
> index 7c11ace..8c4c6a5 100644
> --- a/drivers/cpufreq/exynos4x12-cpufreq.c
> +++ b/drivers/cpufreq/exynos4x12-cpufreq.c
> @@ -30,21 +30,21 @@ static unsigned int exynos4x12_volt_table[] = {
> };
>
> static struct cpufreq_frequency_table exynos4x12_freq_table[] = {
> - {CPUFREQ_BOOST_FREQ, 1500 * 1000},
> - {L1, 1400 * 1000},
> - {L2, 1300 * 1000},
> - {L3, 1200 * 1000},
> - {L4, 1100 * 1000},
> - {L5, 1000 * 1000},
> - {L6, 900 * 1000},
> - {L7, 800 * 1000},
> - {L8, 700 * 1000},
> - {L9, 600 * 1000},
> - {L10, 500 * 1000},
> - {L11, 400 * 1000},
> - {L12, 300 * 1000},
> - {L13, 200 * 1000},
> - {0, CPUFREQ_TABLE_END},
> + {CPUFREQ_BOOST_FREQ, 0, 1500 * 1000},
^^^
Functionally it might make no difference, but may be this line can be
rewritten as:
{CPUFREQ_BOOST_FREQ, L0, 1500 * 1000}
in order to be consistent with the subsequent entries of the table
which use the .driver_data field to record the indices. And L0 has
been defined in exynos-cpufreq.h

But I shall leave it to you and Lukasz to decide if it is worth the
while.

> + {0, L1, 1400 * 1000},
> + {0, L2, 1300 * 1000},
> + {0, L3, 1200 * 1000},
> + {0, L4, 1100 * 1000},
> + {0, L5, 1000 * 1000},
> + {0, L6, 900 * 1000},
> + {0, L7, 800 * 1000},
> + {0, L8, 700 * 1000},
> + {0, L9, 600 * 1000},
> + {0, L10, 500 * 1000},
> + {0, L11, 400 * 1000},
> + {0, L12, 300 * 1000},
> + {0, L13, 200 * 1000},
> + {0, 0, CPUFREQ_TABLE_END},
> };
>

Reviewed-by: Gautham R Shenoy <ego@linux.vnet.ibm.com>

--
Thanks and Regards
gautham.



\
 
 \ /
  Last update: 2014-03-28 12:01    [W:0.112 / U:0.964 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site