cpufreq: s3c64xx: Use cpufreq_for_each_valid_entry macro for iteration
Subsystems (2)
PATCH 12/20 cpufreq: s3c64xx: Use cpufreq_for_each_valid_entry macro for iteration
The cpufreq core supports the cpufreq_for_each_entry and cpufreq_for_each_valid_entry macros helpers for iteration over the cpufreq_frequency_table, so use them.
It should have no functional changes.
Signed-off-by Stratos Karafotis <[email protected]>
--- drivers/cpufreq/s3c64xx-cpufreq.c | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-)
drivers/cpufreq/s3c64xx-cpufreq.c +5 -10
@@ -118,11 +118,10 @@ static void __init s3c64xx_cpufreq_config_regulator(void)pr_err ("Unable to check supported voltages\n" ); } - freq = s3c64xx_freq_table; -while (count >0 && freq->frequency !=CPUFREQ_TABLE_END ) { -if (freq->frequency ==CPUFREQ_ENTRY_INVALID ) -continue ; +if (!count) + goto out; +cpufreq_for_each_valid_entry (freq, s3c64xx_freq_table) { dvfs = &s3c64xx_dvfs_table[freq->driver_data]; found =0 ;
@@ -137,10 +136,9 @@ static void __init s3c64xx_cpufreq_config_regulator(void) freq->frequency); freq->frequency =CPUFREQ_ENTRY_INVALID ; } - - freq++; } +out:/* Guess based on having to do an I2C/SPI write; in future we * will be able to query the regulator performance here. */ regulator_latency =1 *1000 *1000 ;
@@ -179,8 +177,7 @@ static int s3c64xx_cpufreq_driver_init(struct cpufreq_policy *policy) }#endif - freq = s3c64xx_freq_table; -while (freq->frequency !=CPUFREQ_TABLE_END ) { +cpufreq_for_each_entry (freq, s3c64xx_freq_table) {unsigned long r;/* Check for frequencies we can generate */
@@ -196,8 +193,6 @@ static int s3c64xx_cpufreq_driver_init(struct cpufreq_policy *policy)* frequency is the maximum we can support. */ if (!vddarm && freq->frequency >clk_get_rate (policy->clk) /1000 ) freq->frequency =CPUFREQ_ENTRY_INVALID ; - - freq++; }/* Datasheet says PLL stabalisation time (if we were to use
Signature · 1 line
1.9.0