Mark Brown wrote:
>
> By extension from the 667MHz based clocks currently supported add 100MHz
> and 200MHz operating points. Due to a lack of documentation these have not
> been confirmed as supported but by extension from the existing frequencies
> they should be OK, and I've given them quite a bit of runtime testing.
>
> The major risk is synchronization with the non-ARM clocks but as we
> can't currently scale the ARM PLL the risk should be relatively low.
>
> Signed-off-by: Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Acked-by: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@xxxxxxxxxxx>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
> ---
> drivers/cpufreq/s3c64xx-cpufreq.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/cpufreq/s3c64xx-cpufreq.c
b/drivers/cpufreq/s3c64xx-cpufreq.c
> index e818248..b8d1d20 100644
> --- a/drivers/cpufreq/s3c64xx-cpufreq.c
> +++ b/drivers/cpufreq/s3c64xx-cpufreq.c
> @@ -36,7 +36,9 @@ static struct s3c64xx_dvfs s3c64xx_dvfs_table[] = {
>
> static struct cpufreq_frequency_table s3c64xx_freq_table[] = {
> { 0, 66000 },
> + { 0, 100000 },
> { 0, 133000 },
> + { 1, 200000 },
> { 1, 222000 },
> { 1, 266000 },
> { 2, 333000 },
> --
> 1.7.5.4
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
