[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 10 Oct 2017 14:43:01 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Jesper Nilsson <jesper.nilsson@...s.com>
Cc: "rjw@...k.pl" <rjw@...k.pl>,
"linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>,
"patches@...aro.org" <patches@...aro.org>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Jesper Nilsson <jespern@...s.com>,
Mikael Starvik <starvik@...s.com>,
linux-cris-kernel <linux-cris-kernel@...s.com>
Subject: Re: [PATCH 07/34] cpufreq: cris: remove calls to
cpufreq_notify_transition()
On 10-10-17, 09:57, Jesper Nilsson wrote:
> On Fri, Aug 16, 2013 at 04:25:04AM +0200, Viresh Kumar wrote:
> > Most of the drivers do following in their ->target_index() routines:
> >
> > struct cpufreq_freqs freqs;
> > freqs.old = old freq...
> > freqs.new = new freq...
> >
> > cpufreq_notify_transition(policy, &freqs, CPUFREQ_PRECHANGE);
> >
> > /* Change rate here */
> >
> > cpufreq_notify_transition(policy, &freqs, CPUFREQ_POSTCHANGE);
> >
> > This is replicated over all cpufreq drivers today and there doesn't exists a
> > good enough reason why this shouldn't be moved to cpufreq core instead.
> >
> > Earlier patches have added support in cpufreq core to do cpufreq notification on
> > frequency change, this one removes it from this driver.
> >
> > Some related minor cleanups are also done along with it.
> >
>
> Acked-by: Jesper Nilsson <jesper.nilsson@...s.com>
Wow..
You just Acked a 4 years old patch :)
--
viresh
Powered by blists - more mailing lists