From: Xuewen Yan <xuewen.yan@unisoc.com>
To: <lukasz.luba@arm.com>, <rafael@kernel.org>,
<daniel.lezcano@linaro.org>, <rui.zhang@intel.com>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<ke.wang@unisoc.com>, <jeson.gao@unisoc.com>,
<di.shen@unisoc.com>, <xuewen.yan94@gmail.com>
Subject: [RFC PATCH] thermal: power_allocator: Ignore cutoff when integral is less than zero
Date: Mon, 19 Jan 2026 09:58:03 +0800 [thread overview]
Message-ID: <20260119015803.183-1-xuewen.yan@unisoc.com> (raw)
From: Jeson Gao <jeson.gao@unisoc.com>
The cutoff means threshold below which the error is no longer accumulated.
However, in some scenarios, this may cause performance degradation.
For example:
the control-temp is 85, the cutoff is 0 or other small value:
If the current temperature frequently exceeds the set temperature,
the negative integral will continuously accumulate.
Over an extended period, this will result in a significantly
large negative integral value, the positive integral can’t build up
because of the cutoff. This makes the power_range very low,
even if the temperature is already under the control target.
So, if the err_integral is negative, ignore the cutoff to force
add the positive integral.
Co-developed-by: Di Shen <di.shen@unisoc.com>
Signed-off-by: Di Shen <di.shen@unisoc.com>
Signed-off-by: Jeson Gao <jeson.gao@unisoc.com>
Signed-off-by: Xuewen Yan <xuewen.yan@unisoc.com>
---
drivers/thermal/gov_power_allocator.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/thermal/gov_power_allocator.c b/drivers/thermal/gov_power_allocator.c
index 0d9f636c80f4..404ae1d75612 100644
--- a/drivers/thermal/gov_power_allocator.c
+++ b/drivers/thermal/gov_power_allocator.c
@@ -263,7 +263,8 @@ static u32 pid_controller(struct thermal_zone_device *tz,
*/
i = mul_frac(tz->tzp->k_i, params->err_integral);
- if (err < int_to_frac(tz->tzp->integral_cutoff)) {
+ if (err < int_to_frac(tz->tzp->integral_cutoff) ||
+ (err > 0 && params->err_integral < 0)) {
s64 i_next = i + mul_frac(tz->tzp->k_i, err);
if (abs(i_next) < max_power_frac) {
--
2.25.1
next reply other threads:[~2026-01-19 2:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 1:58 Xuewen Yan [this message]
2026-01-26 3:24 ` Xuewen Yan
2026-02-09 12:35 ` Lukasz Luba
2026-02-11 7:43 ` Xuewen Yan
-- strict thread matches above, loose matches on Subject: below --
2026-01-12 5:30 Xuewen Yan
2026-01-12 5:38 ` Xuewen Yan
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=20260119015803.183-1-xuewen.yan@unisoc.com \
--to=xuewen.yan@unisoc.com \
--cc=daniel.lezcano@linaro.org \
--cc=di.shen@unisoc.com \
--cc=jeson.gao@unisoc.com \
--cc=ke.wang@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=xuewen.yan94@gmail.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
all inboxes | Powered by JetHome®