From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: exynos: Broadcast frequency change notifications for all cores
Date: Wed, 21 Nov 2012 22:23:02 +0100 [thread overview]
Message-ID: <3562672.u4N3XIHFEC@flatron> (raw)
In-Reply-To: <4440154.l7bQzsqNex@vostro.rjw.lan>
Hi Rafael,
On Wednesday 21 of November 2012 21:47:42 Rafael J. Wysocki wrote:
> On Wednesday, November 21, 2012 02:52:26 PM Tomasz Figa wrote:
> > On Tuesday 13 of November 2012 10:26:12 Tomasz Figa wrote:
> > > On Exynos SoCs all cores share the same frequency setting, so
> > > changing
> > > frequency of one core will affect rest of cores.
> > >
> > > This patch modifies the exynos-cpufreq driver to inform cpufreq core
> > > about this behavior and broadcast frequency change notifications for
> > > all cores.
> > >
> > > Signed-off-by: Tomasz Figa <t.figa@samsung.com>
> > > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> > > ---
> > >
> > > drivers/cpufreq/exynos-cpufreq.c | 7 +++++--
> > > 1 file changed, 5 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/cpufreq/exynos-cpufreq.c
> > > b/drivers/cpufreq/exynos-cpufreq.c index af2d81e..c0d54a8 100644
> > > --- a/drivers/cpufreq/exynos-cpufreq.c
> > > +++ b/drivers/cpufreq/exynos-cpufreq.c
> > > @@ -100,7 +100,8 @@ static int exynos_target(struct cpufreq_policy
> > > *policy, }
> > >
> > > arm_volt = volt_table[index];
> > >
> > > - cpufreq_notify_transition(&freqs, CPUFREQ_PRECHANGE);
> > > + for_each_cpu(freqs.cpu, policy->cpus)
> > > + cpufreq_notify_transition(&freqs, CPUFREQ_PRECHANGE);
> > >
> > > /* When the new frequency is higher than current frequency */
> > > if ((freqs.new > freqs.old) && !safe_arm_volt) {
> > >
> > > @@ -115,7 +116,8 @@ static int exynos_target(struct cpufreq_policy
> > > *policy, if (freqs.new != freqs.old)
> > >
> > > exynos_info->set_freq(old_index, index);
> > >
> > > - cpufreq_notify_transition(&freqs, CPUFREQ_POSTCHANGE);
> > > + for_each_cpu(freqs.cpu, policy->cpus)
> > > + cpufreq_notify_transition(&freqs, CPUFREQ_POSTCHANGE);
> > >
> > > /* When the new frequency is lower than current frequency */
> > > if ((freqs.new < freqs.old) ||
> > >
> > > @@ -235,6 +237,7 @@ static int exynos_cpufreq_cpu_init(struct
> > > cpufreq_policy *policy) cpumask_copy(policy->related_cpus,
> > > cpu_possible_mask);
> > >
> > > cpumask_copy(policy->cpus, cpu_online_mask);
> > >
> > > } else {
> > >
> > > + policy->shared_type = CPUFREQ_SHARED_TYPE_ANY;
> > >
> > > cpumask_setall(policy->cpus);
> > >
> > > }
> >
> > Ping.
>
> Am I supposed to handle this?
I guess. Would be really nice if you could apply this patch for 3.8.
Best regards,
Tomasz Figa
next prev parent reply other threads:[~2012-11-21 21:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 9:26 [PATCH] cpufreq: exynos: Broadcast frequency change notifications for all cores Tomasz Figa
2012-11-21 13:52 ` Tomasz Figa
2012-11-21 20:47 ` Rafael J. Wysocki
2012-11-21 21:23 ` Tomasz Figa [this message]
2012-11-21 23:41 ` Rafael J. Wysocki
2013-01-31 4:20 ` Viresh Kumar
2013-01-31 14:45 ` Tomasz Figa
2013-01-31 14:52 ` Viresh Kumar
2013-01-31 15:04 ` Tomasz Figa
2013-01-31 15:16 ` Viresh Kumar
2013-01-31 16:07 ` Tomasz Figa
2013-01-31 16:12 ` Viresh Kumar
2013-02-01 3:47 ` 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=3562672.u4N3XIHFEC@flatron \
--to=tomasz.figa@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).