From: Lukasz Luba <lukasz.luba@arm.com>
To: Di Shen <di.shen@unisoc.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
daniel.lezcano@linaro.org, xuewen.yan@unisoc.com,
jeson.gao@unisoc.com, zhanglyra@gmail.com, orsonzhai@gmail.com,
rui.zhang@intel.com, amitk@kernel.org, rafael@kernel.org
Subject: Re: [PATCH V3] thermal/core/power_allocator: avoid thermal cdev can not be reset
Date: Mon, 20 Mar 2023 12:24:07 +0000 [thread overview]
Message-ID: <6055bc39-5c00-d12f-b5c3-fa21a9649d63@arm.com> (raw)
In-Reply-To: <20230320095620.7480-1-di.shen@unisoc.com>
On 3/20/23 09:56, Di Shen wrote:
> Commit <0952177f2a1f>(thermal/core/power_allocator: Update once
> cooling devices when temp is low) adds a update flag to avoid
> the thermal event is triggered when there is no need, and
> thermal cdev would be update once when temperature is low.
>
> But when the trips are writable, and switch_on_temp is set
> to be a higher value, the cooling device state may not be
> reset to 0, because last_temperature is smaller than the
> switch_on_temp.
>
> For example:
> First:
> switch_on_temp=70 control_temp=85;
> Then userspace change the trip_temp:
> switch_on_temp=45 control_temp=55 cur_temp=54
>
> Then userspace reset the trip_temp:
> switch_on_temp=70 control_temp=85 cur_temp=57 last_temp=54
>
> At this time, the cooling device state should be reset to 0.
> However, because cur_temp(57) < switch_on_temp(70)
> last_temp(54) < switch_on_temp(70) ----> update = false,
> update is false, the cooling device state can not be reset.
>
> This patch adds a function thermal_cdev_needs_update() to
> renew the update flag value only when the trips are writable,
> so that thermal cdev->state can be reset after switch_on_temp
> changed from low to high.
>
> Fixes: <0952177f2a1f> (thermal/core/power_allocator: Update once cooling devices when temp is low)
> Signed-off-by: Di Shen <di.shen@unisoc.com>
>
> ---
> V3:
> - Add fix tag.
>
> V2:
> - Compared to v1, do not revert.
>
> - Add a variable(last_switch_on_temp) in power_allocator_params
> to record the last switch_on_temp value.
>
> - Adds a function to renew the update flag and update the
> last_switch_on_temp when thermal trips are writable.
>
> V1:
> - Revert commit 0952177f2a1f.
> ---
> ---
> drivers/thermal/gov_power_allocator.c | 39 ++++++++++++++++++++++-----
> 1 file changed, 33 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/thermal/gov_power_allocator.c b/drivers/thermal/gov_power_allocator.c
> index 0eaf1527d3e3..c9e1f3b15f15 100644
> --- a/drivers/thermal/gov_power_allocator.c
> +++ b/drivers/thermal/gov_power_allocator.c
> @@ -59,6 +59,8 @@ static inline s64 div_frac(s64 x, s64 y)
> * governor switches on when this trip point is crossed.
> * If the thermal zone only has one passive trip point,
> * @trip_switch_on should be INVALID_TRIP.
> + * @last_switch_on_temp:Record the last switch_on_temp only when trips
> + are writable.
> * @trip_max_desired_temperature: last passive trip point of the thermal
> * zone. The temperature we are
> * controlling for.
> @@ -70,6 +72,9 @@ struct power_allocator_params {
> s64 err_integral;
> s32 prev_err;
> int trip_switch_on;
> +#ifdef CONFIG_THERMAL_WRITABLE_TRIPS
> + int last_switch_on_temp;
> +#endif
> int trip_max_desired_temperature;
> u32 sustainable_power;
> };
> @@ -554,6 +559,25 @@ static void get_governor_trips(struct thermal_zone_device *tz,
> }
> }
>
> +#ifdef CONFIG_THERMAL_WRITABLE_TRIPS
> +static bool thermal_cdev_needs_update(struct thermal_zone_device *tz, int switch_on_temp)
> +{
> + bool update;
> + struct power_allocator_params *params = tz->governor_data;
> + int last_switch_on_temp = params->last_switch_on_temp;
> +
> + update = (tz->last_temperature >= last_switch_on_temp);
> + params->last_switch_on_temp = switch_on_temp;
> +
> + return update;
> +}
> +#else
> +static inline bool thermal_cdev_needs_update(struct thermal_zone_device *tz, int switch_on_temp)
> +{
> + return false;
> +}
> +#endif
> +
> static void reset_pid_controller(struct power_allocator_params *params)
> {
> params->err_integral = 0;
> @@ -709,12 +733,15 @@ static int power_allocator_throttle(struct thermal_zone_device *tz, int trip_id)
> return 0;
>
> ret = __thermal_zone_get_trip(tz, params->trip_switch_on, &trip);
> - if (!ret && (tz->temperature < trip.temperature)) {
> - update = (tz->last_temperature >= trip.temperature);
> - tz->passive = 0;
> - reset_pid_controller(params);
> - allow_maximum_power(tz, update);
> - return 0;
> + if (!ret) {
> + update = thermal_cdev_needs_update(tz, trip.temperature);
> + if (tz->temperature < trip.temperature) {
> + update |= (tz->last_temperature >= trip.temperature);
> + tz->passive = 0;
> + reset_pid_controller(params);
> + allow_maximum_power(tz, update);
> + return 0;
> + }
> }
>
> tz->passive = 1;
Thanks for the patch. The code looks good. The initial value of
'last_switch_on_temp' would be set to 0. It won't harm us because it
will get the proper value later.
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
next prev parent reply other threads:[~2023-03-20 12:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 9:56 Di Shen
2023-03-20 12:24 ` Lukasz Luba [this message]
2023-04-10 2:09 ` Di Shen
2023-04-10 19:51 ` Daniel Lezcano
2023-04-11 7:17 ` Lukasz Luba
2023-04-13 4:51 ` Di Shen
2023-04-13 7:37 ` Daniel Lezcano
2023-04-13 8:40 ` Di Shen
2023-04-14 11:12 ` Daniel Lezcano
2023-04-14 14:18 ` Lukasz Luba
2023-04-14 15:06 ` Daniel Lezcano
2023-04-14 15:21 ` Lukasz Luba
2023-05-25 6:39 ` Di Shen
2023-06-19 6:35 ` [PATCH V4] thermal/core/power_allocator: reset thermal governor when trip point is changed Di Shen
2023-06-20 9:46 ` Rafael J. Wysocki
2023-06-20 10:07 ` Rafael J. Wysocki
2023-06-20 10:20 ` Lukasz Luba
2023-06-20 10:39 ` Rafael J. Wysocki
2023-06-20 11:56 ` Lukasz Luba
2023-06-22 18:27 ` Rafael J. Wysocki
2023-06-23 7:43 ` Lukasz Luba
2023-06-23 16:55 ` Rafael J. Wysocki
2023-06-23 17:34 ` Lukasz Luba
2023-06-25 8:40 ` Di Shen
2023-06-25 8:39 ` Di Shen
2023-06-26 7:45 ` Lukasz Luba
2023-06-20 10:38 ` Lukasz Luba
2023-06-21 4:51 ` Di Shen
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=6055bc39-5c00-d12f-b5c3-fa21a9649d63@arm.com \
--to=lukasz.luba@arm.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=di.shen@unisoc.com \
--cc=jeson.gao@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=xuewen.yan@unisoc.com \
--cc=zhanglyra@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®