From: 함명주 <myungjoo.ham@samsung.com>
To: Tushar Behera <tushar.behera@linaro.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>
Cc: "davej@redhat.com" <davej@redhat.com>, 이재철 <jc.lee@samsung.com>
Subject: Re: Re: [PATCH] EXYNOS: Initialize locking_frequency with initial frequency
Date: Thu, 09 Feb 2012 05:35:09 +0000 (GMT) [thread overview]
Message-ID: <22312902.436411328765708629.JavaMail.weblogic@epml10> (raw)
> On 02/01/2012 04:38 PM, Tushar Behera wrote:
> > On 01/25/2012 10:15 AM, Tushar Behera wrote:
> >> As per definition, locking_frequency is the initial frequency which is
> >> set by boot-loader. Hence the value is updated with the initial value
> >> during boot time init call.
> >>
> >> This code was present in exynos210-cpufreq.c before this consolidation
> >> patch.
> >> - a125a17fa61a ([CPUFREQ] EXYNOS: Make EXYNOS common cpufreq driver).
> >>
> >> Signed-off-by: Tushar Behera <tushar.behera@linaro.org>
> >> Signed-off-by: Inderpal Singh <inderpal.singh@linaro.org>
Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
> >> ---
> >> The patch is based on v3.3-rc1.
> >>
> >> drivers/cpufreq/exynos-cpufreq.c | 2 ++
> >> 1 files changed, 2 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufreq/exynos-cpufreq.c
> >> index 5467879..7cfb516 100644
> >> --- a/drivers/cpufreq/exynos-cpufreq.c
> >> +++ b/drivers/cpufreq/exynos-cpufreq.c
> >> @@ -210,6 +210,8 @@ 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;
> >>
> >
> >
>
>
> --
> Tushar Behera
>
>
reply other threads:[~2012-02-09 5:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=22312902.436411328765708629.JavaMail.weblogic@epml10 \
--to=myungjoo.ham@samsung.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=jc.lee@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tushar.behera@linaro.org \
/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