linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukasz Luba <lukasz.luba@arm.com>
To: daniel.lezcano@linaro.org
Cc: amit.kachhap@gmail.com, viresh.kumar@linaro.org,
	rafael@kernel.org, amitk@kernel.org, rui.zhang@intel.com,
	dietmar.eggemann@arm.com, Pierre.Gondois@arm.com,
	Matthias Kaehlcke <mka@chromium.org>,
	Doug Anderson <dianders@chromium.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] thermal: cooling: Check Energy Model type in cpufreq_cooling and devfreq_cooling
Date: Tue, 22 Feb 2022 17:05:13 +0000	[thread overview]
Message-ID: <211a3606-2f4c-227b-33aa-177ef68a49a3@arm.com> (raw)
In-Reply-To: <4e090ffe-c19b-8e2c-0396-72dc33361f35@arm.com>

Hi Daniel,

gentle ping

On 2/17/22 18:18, Lukasz Luba wrote:
> Hi Daniel,
> 
> 
> On 2/7/22 7:30 AM, Lukasz Luba wrote:
>> The Energy Model supports power values either in Watts or in some 
>> abstract
>> scale. When the 2nd option is in use, the thermal governor IPA should not
>> be allowed to operate, since the relation between cooling devices is not
>> properly defined. Thus, it might be possible that big GPU has lower power
>> values in abstract scale than a Little CPU. To mitigate a misbehaviour
>> of the thermal control algorithm, simply not register a cooling device
>> capable of working with IPA.
>>
>> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
>> ---
>>   drivers/thermal/cpufreq_cooling.c |  2 +-
>>   drivers/thermal/devfreq_cooling.c | 16 +++++++++++++---
>>   2 files changed, 14 insertions(+), 4 deletions(-)
> 
> The discussion in below this patch went slightly off-topic but it was
> valuable. It clarified also there are no broken platforms with this
> change.
> 
> Could you take the patch into the thermal tree, please?
> 
> Regards,
> Lukasz

  reply	other threads:[~2022-02-22 17:05 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07  7:30 [PATCH 0/2] Ignore Energy Model with abstract scale in IPA and DTPM Lukasz Luba
2022-02-07  7:30 ` [PATCH 1/2] thermal: cooling: Check Energy Model type in cpufreq_cooling and devfreq_cooling Lukasz Luba
2022-02-08  0:50   ` Matthias Kaehlcke
2022-02-08  9:32     ` Lukasz Luba
2022-02-08 17:25       ` Matthias Kaehlcke
2022-02-09 11:16         ` Lukasz Luba
2022-02-09 22:17           ` Matthias Kaehlcke
2022-02-16 15:35             ` Lukasz Luba
2022-02-16 17:33               ` Doug Anderson
2022-02-16 22:13                 ` Matthias Kaehlcke
2022-02-16 22:43                   ` Lukasz Luba
2022-02-17  0:26                     ` Matthias Kaehlcke
2022-02-17 10:15                     ` Daniel Lezcano
2022-02-17  9:59                   ` Daniel Lezcano
2022-02-17 10:10                 ` Daniel Lezcano
2022-02-17 10:47                   ` Lukasz Luba
2022-02-17 11:28                     ` Daniel Lezcano
2022-02-17 12:11                       ` Lukasz Luba
2022-02-17 12:33                         ` Daniel Lezcano
2022-02-17 12:37                           ` Lukasz Luba
2022-02-17 16:46                         ` Matthias Kaehlcke
2022-02-17 16:37                     ` Doug Anderson
2022-02-17 17:14                       ` Matthias Kaehlcke
2022-02-17 18:05                         ` Lukasz Luba
2022-02-17 18:27                       ` Daniel Lezcano
2022-02-16 17:21       ` Doug Anderson
2022-02-16 23:28         ` Lukasz Luba
2022-02-17 16:50           ` Doug Anderson
2022-02-17 17:58             ` Lukasz Luba
2022-02-17 18:18   ` Lukasz Luba
2022-02-22 17:05     ` Lukasz Luba [this message]
2022-02-22 18:12       ` Daniel Lezcano
2022-02-22 18:31         ` Lukasz Luba
2022-02-22 22:10           ` Daniel Lezcano
2022-02-23  9:10             ` Lukasz Luba
2022-02-07  7:30 ` [PATCH 2/2] powercap: DTPM: Check Energy Model type for power values scale Lukasz Luba
2022-02-07 10:41 ` [PATCH 0/2] Ignore Energy Model with abstract scale in IPA and DTPM Daniel Lezcano
2022-02-07 11:44   ` Lukasz Luba
2022-02-08  7:39     ` Daniel Lezcano
2022-02-08  9:47       ` Lukasz Luba

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=211a3606-2f4c-227b-33aa-177ef68a49a3@arm.com \
    --to=lukasz.luba@arm.com \
    --cc=Pierre.Gondois@arm.com \
    --cc=amit.kachhap@gmail.com \
    --cc=amitk@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=dianders@chromium.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=viresh.kumar@linaro.org \
    /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).