From: Kukjin Kim <kgene@kernel.org>
To: 'amit daniel kachhap' <amit.daniel@samsung.com>,
'Viresh Kumar' <viresh.kumar@linaro.org>
Cc: "'Rafael J. Wysocki'" <rjw@sisk.pl>,
'linaro-kernel' <linaro-kernel@lists.linaro.org>,
patches@linaro.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RE: [PATCH 13/37] cpufreq: exynos: don't initialize part of policy that is set by core too
Date: Mon, 19 Aug 2013 06:58:31 +0900 [thread overview]
Message-ID: <15fc01ce9c5e$13e53390$3baf9ab0$@org> (raw)
In-Reply-To: <CADGdYn5nPCOb=mqoJPXzbZzgnbfrhFX6+nsUO5h+PTc-M=2NFA@mail.gmail.com>
amit daniel kachhap wrote:
>
> On Wed, Aug 14, 2013 at 7:02 PM, Viresh Kumar <viresh.kumar@linaro.org>
> wrote:
> > Many common initializations of struct policy are moved to core now and
> hence
> > this driver doesn't need to do it. This patch removes such code.
> >
> > Most recent of those changes is to call ->get() in the core after
> calling
> > ->init().
> >
> > Cc: Kukjin Kim <kgene.kim@samsung.com>
Acked-by: Kukjin Kim <kgene.kim@samsung.com>
Thanks,
Kukjin
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> This consolidation work looks fine,
> Acked-By: Amit Daniel Kachhap <amit.daniel@samsung.com>
>
> Thanks,
> Amit
> > ---
> > drivers/cpufreq/exynos-cpufreq.c | 2 --
> > drivers/cpufreq/exynos5440-cpufreq.c | 1 -
> > 2 files changed, 3 deletions(-)
> >
> > diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufreq/exynos-
> cpufreq.c
> > index 79b869b..b1db082 100644
> > --- a/drivers/cpufreq/exynos-cpufreq.c
> > +++ b/drivers/cpufreq/exynos-cpufreq.c
> > @@ -226,8 +226,6 @@ static struct notifier_block exynos_cpufreq_nb = {
> >
> > static int exynos_cpufreq_cpu_init(struct cpufreq_policy *policy)
> > {
> > - policy->cur = policy->min = policy->max =
exynos_getspeed(policy-
> >cpu);
> > -
> > /* set the transition latency value */
> > policy->cpuinfo.transition_latency = 100000;
> >
> > diff --git a/drivers/cpufreq/exynos5440-cpufreq.c
> b/drivers/cpufreq/exynos5440-cpufreq.c
> > index 9a5ed485..91a64d6 100644
> > --- a/drivers/cpufreq/exynos5440-cpufreq.c
> > +++ b/drivers/cpufreq/exynos5440-cpufreq.c
> > @@ -316,7 +316,6 @@ static int exynos_cpufreq_cpu_init(struct
> cpufreq_policy *policy)
> > return ret;
> > }
> >
> > - policy->cur = dvfs_info->cur_frequency;
> > policy->cpuinfo.transition_latency = dvfs_info->latency;
> > cpumask_setall(policy->cpus);
> >
> > --
> > 1.7.12.rc2.18.g61b472e
next prev parent reply other threads:[~2013-08-18 21:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 13:31 [PATCH 00/37] CPUFreq: set policy->cur in cpufreq core instead of Viresh Kumar
2013-08-14 13:31 ` [PATCH 01/37] cpufreq: call cpufreq_driver->get() after calling ->init() Viresh Kumar
2013-08-14 13:31 ` [PATCH 02/37] cpufreq: acpi: don't initialize part of policy that is set by core too Viresh Kumar
2013-08-14 13:31 ` [PATCH 03/37] cpufreq: arm_big_little: " Viresh Kumar
2013-08-14 13:31 ` [PATCH 04/37] cpufreq: at32ap: " Viresh Kumar
2013-08-14 14:35 ` Hans-Christian Egtvedt
2013-08-14 14:37 ` Viresh Kumar
2013-08-14 14:44 ` Hans-Christian Egtvedt
2013-08-14 13:31 ` [PATCH 05/37] cpufreq: blackfin: " Viresh Kumar
2013-08-14 13:31 ` [PATCH 06/37] cpufreq: cpu0: " Viresh Kumar
2013-08-14 13:31 ` [PATCH 07/37] cpufreq: nforce2: " Viresh Kumar
2013-08-14 13:31 ` [PATCH 08/37] cpufreq: cris: " Viresh Kumar
2013-08-14 13:31 ` [PATCH 09/37] cpufreq: davinci: " Viresh Kumar
2013-08-14 13:31 ` [PATCH 10/37] cpufreq: dbx500: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 11/37] cpufreq: e_powersaver: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 12/37] cpufreq: elanfreq: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 13/37] cpufreq: exynos: " Viresh Kumar
2013-08-18 10:50 ` amit daniel kachhap
2013-08-18 21:58 ` Kukjin Kim [this message]
2013-08-14 13:32 ` [PATCH 14/37] cpufreq: gx: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 15/37] cpufreq: ia64-acpi: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 16/37] cpufreq: imx6q: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 17/37] cpufreq: integrator: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 18/37] cpufreq: kirkwood: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 19/37] cpufreq: longhaul: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 20/37] cpufreq: loongson2: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 21/37] cpufreq: maple: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 22/37] cpufreq: omap: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 23/37] cpufreq: p4: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 24/37] cpufreq: pcc: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 25/37] cpufreq: pmac: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 26/37] cpufreq: powernow: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 27/37] cpufreq: ppc: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 28/37] cpufreq: pxa: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 29/37] cpufreq: s3c: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 30/37] cpufreq: s5pv210: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 31/37] cpufreq: sa11x0: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 32/37] cpufreq: sc520_freq: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 33/37] cpufreq: sh: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 34/37] cpufreq: spear: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 35/37] cpufreq: speedstep: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 36/37] cpufreq: tegra: " Viresh Kumar
2013-08-14 13:32 ` [PATCH 37/37] cpufreq: unicore2: " Viresh Kumar
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='15fc01ce9c5e$13e53390$3baf9ab0$@org' \
--to=kgene@kernel.org \
--cc=amit.daniel@samsung.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@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;
as well as URLs for NNTP newsgroup(s).