From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-pm@vger.kernel.org, linux-wireless@vger.kernel.org,
daniel.lezcano@linaro.org, andrzej.p@collabora.com,
luca@coelho.fi
Subject: Re: [PATCH 3/6] thermal: core: update polling after all trips handled
Date: Mon, 4 May 2020 09:01:46 +0200 [thread overview]
Message-ID: <918bfe45-511a-e527-7950-c19a64f29f40@samsung.com> (raw)
In-Reply-To: <20200430063229.6182-4-rui.zhang@intel.com>
On 4/30/20 8:32 AM, Zhang Rui wrote:
> Move monitor_thermal_zone() from handle_thermal_trip() to
> thermal_zone_device_update() because updating the polling timers after all
> trips handled is sufficient.
>
> Signed-off-by: Zhang Rui <rui.zhang@intel.com>
Reviewed-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
> ---
> drivers/thermal/thermal_core.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
> index ac70545..04a16a9 100644
> --- a/drivers/thermal/thermal_core.c
> +++ b/drivers/thermal/thermal_core.c
> @@ -430,11 +430,6 @@ static void handle_thermal_trip(struct thermal_zone_device *tz, int trip)
> handle_critical_trips(tz, trip, type);
> else
> handle_non_critical_trips(tz, trip);
> - /*
> - * Alright, we handled this trip successfully.
> - * So, start monitoring again.
> - */
> - monitor_thermal_zone(tz);
> }
>
> static void update_temperature(struct thermal_zone_device *tz)
> @@ -529,6 +524,12 @@ void thermal_zone_device_update(struct thermal_zone_device *tz,
>
> for (count = 0; count < tz->trips; count++)
> handle_thermal_trip(tz, count);
> +
> + /*
> + * Alright, we handled all the trips successfully.
> + * So, start monitoring again.
> + */
> + monitor_thermal_zone(tz);
> }
> EXPORT_SYMBOL_GPL(thermal_zone_device_update);
>
next prev parent reply other threads:[~2020-05-04 7:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 6:32 [PATCH 0/6] thermal: improve handling of disabled thermal zone Zhang Rui
2020-04-30 6:32 ` [PATCH 1/6] iwlwifi: use thermal_zone_device_update() for temperature change Zhang Rui
2020-05-12 1:58 ` Zhang Rui
2020-05-18 11:21 ` Luca Coelho
2020-05-25 6:04 ` Zhang Rui
2020-05-25 13:33 ` Rafael J. Wysocki
2020-04-30 6:32 ` [PATCH 2/6] thermal: core: delete thermal_notify_framework() Zhang Rui
2020-04-30 8:47 ` Andrzej Pietrasiewicz
2020-04-30 8:58 ` Zhang, Rui
2020-04-30 11:32 ` Andrzej Pietrasiewicz
2020-04-30 11:33 ` Andrzej Pietrasiewicz
2020-05-04 10:18 ` Andrzej Pietrasiewicz
2020-04-30 6:32 ` [PATCH 3/6] thermal: core: update polling after all trips handled Zhang Rui
2020-05-04 7:01 ` Bartlomiej Zolnierkiewicz [this message]
2020-04-30 6:32 ` [PATCH 4/6] thermal: core: stop polling timer for disabled thermal zone Zhang Rui
2020-05-04 7:02 ` Bartlomiej Zolnierkiewicz
2020-04-30 6:32 ` [PATCH 5/6] thermal: core: introduce tz_disabled() helper function Zhang Rui
2020-05-04 7:09 ` Bartlomiej Zolnierkiewicz
2020-05-12 1:59 ` Zhang Rui
2020-04-30 6:32 ` [PATCH RFC 6/6] iwlwifi: enable thermal zone only when firmware loaded Zhang Rui
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=918bfe45-511a-e527-7950-c19a64f29f40@samsung.com \
--to=b.zolnierkie@samsung.com \
--cc=andrzej.p@collabora.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
--cc=rui.zhang@intel.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