[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161005052137.GL4664@vireshk-i7>
Date: Wed, 5 Oct 2016 10:51:37 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Andreas Herrmann <aherrmann@...e.com>
Cc: Stratos Karafotis <skarafotis@...il.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Stratos Karafotis <stratosk@...aphore.gr>,
Thomas Renninger <trenn@...e.com>
Subject: Re: [PATCH 1/1] cpufreq: pcc-cpufreq: Re-introduce deadband effect
to reduce number of frequency changes
On 22-09-16, 19:54, Andreas Herrmann wrote:
> On Mon, Sep 19, 2016 at 10:39:18PM +0300, Stratos Karafotis wrote:
> > Just an idea. I would split the frequency range (max_freq - min_freq)
> > into ~10 steps. But I'm not familiar with the affected systems and
> > of course I can't prove this is an ideal approach.
>
> I've modified the pcc-cpufreq specific map_load_to_freq function to do
> just that (map load values to 10 discrete frequency values) instead of
> falling back to the deadband (pre-commit-6393d6-version).
And in that you can remove the deadband frequencies from the table to
get almost the same results, as I already stated in an earlier email.
--
viresh
Powered by blists - more mailing lists