linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Quentin Perret <quentin.perret@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-pm@vger.kernel.org, rjw@rjwysocki.net,
	amit.kachhap@gmail.com, daniel.lezcano@linaro.org,
	will.deacon@arm.com, linux-kernel@vger.kernel.org,
	edubezval@gmail.com, catalin.marinas@arm.com,
	rui.zhang@intel.com, javi.merino@kernel.org,
	ionela.voinescu@arm.com, dietmar.eggemann@arm.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] thermal: cpu_cooling: Migrate to using the EM framework
Date: Wed, 10 Apr 2019 09:57:04 +0100	[thread overview]
Message-ID: <20190410085702.nll6spd565oio3ds@queper01-lin> (raw)
In-Reply-To: <20190410054449.zwmemg7vza557gue@vireshk-i7>

On Wednesday 10 Apr 2019 at 11:14:49 (+0530), Viresh Kumar wrote:
> On 28-03-19, 10:13, Quentin Perret wrote:
> > +static unsigned int get_state_freq(struct cpufreq_cooling_device *cpufreq_cdev,
> > +			      unsigned long state)
> > +{
> > +	struct cpufreq_policy *policy;
> > +	unsigned long idx;
> > +
> > +	/* Use the Energy Model table if available */
> > +	if (cpufreq_cdev->em) {
> > +		idx = cpufreq_cdev->max_level - state;
> > +		return cpufreq_cdev->em->table[idx].frequency;
> > +	}
> > +
> > +	/* Otherwise, fallback on the CPUFreq table */
> > +	policy = cpufreq_cdev->policy;
> > +	if (policy->freq_table_sorted == CPUFREQ_TABLE_SORTED_ASCENDING)
> 
> It is not guaranteed that the frequency table is sorted in any order, isn't it ?

Hmm, indeed... I thought cpufreq_table_validate_and_sort() was actively
sorting the table but it seems I was wrong.

But I _think_ in practice the freq table actually happens to be sorted
for the upstream cpufreq drivers with the CPUFREQ_IS_COOLING_DEV flag
set. Most of them use dev_pm_opp_init_cpufreq_table() which guarantees
the table is sorted and qoriq-cpufreq explicitly sorts the table. But
I'm not sure about qcom-cpufreq-hw ...

So, if the above is true, perhaps I could simply add a check to mandate
that policy->freq_table_sorted != CPUFREQ_TABLE_SORTED_UNSORTED for
cpu_cooling ? That shouldn't harm the existing users.

Do you happen to know a board where the table is unsorted ? Is it a
common use-case ?

If yes, then I'll probably need to drop the dependency on cpufreq's
freq_table and use something else to convert indexes into frequencies
(PM_OPP ?). Unless we can force-sort the table in the cpufreq core, but
that might require lots of changes to lots of drivers too.

> 
> > +		idx = cpufreq_cdev->max_level - state;
> > +	else
> > +		idx = state;
> 
> -- 
> viresh

Thanks,
Quentin

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-04-10  8:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 10:13 [PATCH 0/3] cpu_cooling: Make IPA use PM_EM Quentin Perret
2019-03-28 10:13 ` [PATCH 1/3] arm64: defconfig: Enable CONFIG_ENERGY_MODEL Quentin Perret
2019-03-28 10:22   ` Quentin Perret
2019-03-28 17:27     ` Daniel Lezcano
2019-03-28 17:42       ` Quentin Perret
2019-03-28 19:51         ` Daniel Lezcano
2019-03-29  9:03           ` Quentin Perret
2019-03-28 10:13 ` [PATCH 2/3] PM / EM: Expose perf domain struct Quentin Perret
2019-03-28 10:13 ` [PATCH 3/3] thermal: cpu_cooling: Migrate to using the EM framework Quentin Perret
2019-03-28 20:23   ` Daniel Lezcano
2019-03-29  9:16     ` Quentin Perret
2019-03-29 17:17       ` Daniel Lezcano
2019-04-10  5:44   ` Viresh Kumar
2019-04-10  8:57     ` Quentin Perret [this message]
2019-04-10 10:14       ` Viresh Kumar
2019-04-10 10:36         ` Quentin Perret

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=20190410085702.nll6spd565oio3ds@queper01-lin \
    --to=quentin.perret@arm.com \
    --cc=amit.kachhap@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=edubezval@gmail.com \
    --cc=ionela.voinescu@arm.com \
    --cc=javi.merino@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=viresh.kumar@linaro.org \
    --cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).