public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Quentin Perret <quentin.perret@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: edubezval@gmail.com, rui.zhang@intel.com, javi.merino@kernel.org,
	amit.kachhap@gmail.com, rjw@rjwysocki.net, will.deacon@arm.com,
	catalin.marinas@arm.com, daniel.lezcano@linaro.org,
	dietmar.eggemann@arm.com, ionela.voinescu@arm.com,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	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 11:36:45 +0100	[thread overview]
Message-ID: <20190410103642.gopsoixrpc4nfuxz@queper01-lin> (raw)
In-Reply-To: <20190410101423.3pl6yfhv2wnxuwgw@vireshk-i7>

On Wednesday 10 Apr 2019 at 15:44:23 (+0530), Viresh Kumar wrote:
> On 10-04-19, 09:57, Quentin Perret wrote:
> > 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.
> 
> Right, I think most of the platforms will have it sorted anyway right now, but
> you never know if one or two of them don't. Maybe just add the above conditional
> and put out an error or WARN or something, so people know that something broke.

Right, WARN + bail out should do it. I'll do the change in v2.

Thanks !
Quentin

  parent reply	other threads:[~2019-04-10 10:36 UTC|newest]

Thread overview: 20+ 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  5:44     ` Viresh Kumar
2019-04-10  8:57     ` Quentin Perret
2019-04-10  8:57       ` Quentin Perret
2019-04-10 10:14       ` Viresh Kumar
2019-04-10 10:14         ` Viresh Kumar
2019-04-10 10:36         ` Quentin Perret [this message]
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=20190410103642.gopsoixrpc4nfuxz@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