From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Jonghwan Choi' <jhbird.choi@samsung.com>,
linux-samsung-soc@vger.kernel.org
Cc: 'Jaecheol Lee' <jc.lee@samsung.com>,
"'Rafael J. Wysocki'" <rjw@sisk.pl>,
'Russell King' <linux@arm.linux.org.uk>
Subject: RE: [PATCH] cpufreq: exynos: Get booting freq value in exynos_cpufreq_init
Date: Thu, 17 Jan 2013 20:34:30 -0800 [thread overview]
Message-ID: <00e201cdf535$1ce7d680$56b78380$@samsung.com> (raw)
In-Reply-To: <00b801cdecb1$57d55e20$07801a60$%choi@samsung.com>
Jonghwan Choi wrote:
>
> Boot_freq is for saving booting freq. But exynos_cpufreq_cpu_init
> is called in hotplug. If boot_freq is existed in exynos_cpufreq_cpu_init,
> boot_freq could be changed.
>
> Signed-off-by: Jonghwan Choi <jhbird.choi@samsung.com>
> ---
> drivers/cpufreq/exynos-cpufreq.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/exynos-cpufreq.c
> b/drivers/cpufreq/exynos-cpufreq.c
> index 7012ea8..41fc550 100644
> --- a/drivers/cpufreq/exynos-cpufreq.c
> +++ b/drivers/cpufreq/exynos-cpufreq.c
> @@ -222,8 +222,6 @@ static int exynos_cpufreq_cpu_init(struct
> cpufreq_policy
> *policy)
>
> cpufreq_frequency_table_get_attr(exynos_info->freq_table,
> policy->cpu);
>
> - locking_frequency = exynos_getspeed(0);
> -
> /* set the transition latency value */
> policy->cpuinfo.transition_latency = 100000;
>
> @@ -288,6 +286,8 @@ static int __init exynos_cpufreq_init(void)
> goto err_vdd_arm;
> }
>
> + locking_frequency = exynos_getspeed(0);
> +
> register_pm_notifier(&exynos_cpufreq_nb);
>
> if (cpufreq_register_driver(&exynos_driver)) {
> --
> 1.7.4.1
Applied, thanks.
- Kukjin
prev parent reply other threads:[~2013-01-18 4:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 8:31 [PATCH] cpufreq: exynos: Get booting freq value in exynos_cpufreq_init Jonghwan Choi
2013-01-18 4:34 ` Kukjin Kim [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00e201cdf535$1ce7d680$56b78380$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=jc.lee@samsung.com \
--cc=jhbird.choi@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox