From: Ralf Baechle <ralf@linux-mips.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
wuzhangjin@gmail.com, linux-mips@linux-mips.org,
tglx@linutronix.de, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] CPUFREQ: Loongson2: drop set_cpus_allowed_ptr()
Date: Mon, 10 Apr 2017 13:05:11 +0200 [thread overview]
Message-ID: <20170410110511.GE24214@linux-mips.org> (raw)
In-Reply-To: <20170410103153.GK24555@vireshk-i7>
On Mon, Apr 10, 2017 at 04:01:53PM +0530, Viresh Kumar wrote:
> On 04-04-17, 17:49, Sebastian Andrzej Siewior wrote:
> > It is pure mystery to me why we need to be on a specific CPU while
> > looking up a value in an array.
> > My best shot at this is that before commit d4019f0a92ab ("cpufreq: move
> > freq change notifications to cpufreq core") it was required to invoke
> > cpufreq_notify_transition() on a special CPU.
> >
> > Since it looks like a waste, remove it.
> >
> > Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> > Cc: Viresh Kumar <viresh.kumar@linaro.org>
> > Cc: linux-pm@vger.kernel.org
> > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> > ---
> > drivers/cpufreq/loongson2_cpufreq.c | 7 -------
> > 1 file changed, 7 deletions(-)
> >
> > diff --git a/drivers/cpufreq/loongson2_cpufreq.c b/drivers/cpufreq/loongson2_cpufreq.c
> > index 6bbdac1065ff..9ac27b22476c 100644
> > --- a/drivers/cpufreq/loongson2_cpufreq.c
> > +++ b/drivers/cpufreq/loongson2_cpufreq.c
> > @@ -51,19 +51,12 @@ static int loongson2_cpu_freq_notifier(struct notifier_block *nb,
> > static int loongson2_cpufreq_target(struct cpufreq_policy *policy,
> > unsigned int index)
> > {
> > - unsigned int cpu = policy->cpu;
> > - cpumask_t cpus_allowed;
> > unsigned int freq;
> >
> > - cpus_allowed = current->cpus_allowed;
> > - set_cpus_allowed_ptr(current, cpumask_of(cpu));
> > -
> > freq =
> > ((cpu_clock_freq / 1000) *
> > loongson2_clockmod_table[index].driver_data) / 8;
> >
> > - set_cpus_allowed_ptr(current, &cpus_allowed);
> > -
> > /* setting the cpu frequency */
> > clk_set_rate(policy->clk, freq * 1000);
>
> It was Zhangjin who wrote the first version and he may be able to
> answer the questions we have. Anyway, it is safe to apply this patch
> right now.
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Thanks for the ack, patch applied.
I noticed some of the other cpufreq drivers seem to be using similar
constructs.
Ralf
next prev parent reply other threads:[~2017-04-10 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 15:49 [PATCH] CPUFREQ: Loongson2: drop set_cpus_allowed_ptr() Sebastian Andrzej Siewior
2017-04-10 10:31 ` Viresh Kumar
2017-04-10 11:05 ` Ralf Baechle [this message]
2017-04-10 11:11 ` Sebastian Andrzej Siewior
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=20170410110511.GE24214@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=bigeasy@linutronix.de \
--cc=linux-mips@linux-mips.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=wuzhangjin@gmail.com \
/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