mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lukasz Luba <lukasz.luba@arm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH v2 02/12] thermal: core: Rearrange PM notification code
Date: Mon, 21 Oct 2024 23:18:24 +0100	[thread overview]
Message-ID: <24c31077-8970-4fcd-bcaa-60d1a3da8f27@arm.com> (raw)
In-Reply-To: <2299090.iZASKD2KPV@rjwysocki.net>



On 10/4/24 20:09, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
> Move the code run for each thermal zone by the thermal PM notify
> handler to separate functions.
> 
> This will help to make some subsequent changes look somewhat more
> straightforward, among other things.
> 
> No intentional functional impact.
> 
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> 
> This is a new iteration of
> 
> https://lore.kernel.org/linux-pm/4940614.GXAFRqVoOG@rjwysocki.net/
> 
> v1 -> v2: The thermal zone guard has not been defined yet, so use lock/unlock
>            directly on the thermal zone lock and update the changelog accordingly.
> 
> ---
>   drivers/thermal/thermal_core.c |   88 +++++++++++++++++++++--------------------
>   1 file changed, 46 insertions(+), 42 deletions(-)
> 
> Index: linux-pm/drivers/thermal/thermal_core.c
> ===================================================================
> --- linux-pm.orig/drivers/thermal/thermal_core.c
> +++ linux-pm/drivers/thermal/thermal_core.c
> @@ -1675,6 +1675,48 @@ static void thermal_zone_device_resume(s
>   	mutex_unlock(&tz->lock);
>   }
>   
> +static void thermal_zone_pm_prepare(struct thermal_zone_device *tz)
> +{
> +	mutex_lock(&tz->lock);
> +
> +	if (tz->resuming) {
> +		/*
> +		 * thermal_zone_device_resume() queued up for this zone has not
> +		 * acquired the lock yet, so release it to let the function run
> +		 * and wait util it has done the work.
> +		 */
> +		mutex_unlock(&tz->lock);
> +
> +		wait_for_completion(&tz->resume);
> +
> +		mutex_lock(&tz->lock);
> +	}
> +
> +	tz->suspended = true;
> +
> +	mutex_unlock(&tz->lock);
> +}
> +
> +static void thermal_zone_pm_complete(struct thermal_zone_device *tz)
> +{
> +	mutex_lock(&tz->lock);
> +
> +	cancel_delayed_work(&tz->poll_queue);
> +
> +	reinit_completion(&tz->resume);
> +	tz->resuming = true;
> +
> +	/*
> +	 * Replace the work function with the resume one, which will restore the
> +	 * original work function and schedule the polling work if needed.
> +	 */
> +	INIT_DELAYED_WORK(&tz->poll_queue, thermal_zone_device_resume);
> +	/* Queue up the work without a delay. */
> +	mod_delayed_work(system_freezable_power_efficient_wq, &tz->poll_queue, 0);
> +
> +	mutex_unlock(&tz->lock);
> +}
> +
>   static int thermal_pm_notify(struct notifier_block *nb,
>   			     unsigned long mode, void *_unused)
>   {
> @@ -1686,27 +1728,8 @@ static int thermal_pm_notify(struct noti
>   	case PM_SUSPEND_PREPARE:
>   		mutex_lock(&thermal_list_lock);
>   
> -		list_for_each_entry(tz, &thermal_tz_list, node) {
> -			mutex_lock(&tz->lock);
> -
> -			if (tz->resuming) {
> -				/*
> -				 * thermal_zone_device_resume() queued up for
> -				 * this zone has not acquired the lock yet, so
> -				 * release it to let the function run and wait
> -				 * util it has done the work.
> -				 */
> -				mutex_unlock(&tz->lock);
> -
> -				wait_for_completion(&tz->resume);
> -
> -				mutex_lock(&tz->lock);
> -			}
> -
> -			tz->suspended = true;
> -
> -			mutex_unlock(&tz->lock);
> -		}
> +		list_for_each_entry(tz, &thermal_tz_list, node)
> +			thermal_zone_pm_prepare(tz);
>   
>   		mutex_unlock(&thermal_list_lock);
>   		break;
> @@ -1715,27 +1738,8 @@ static int thermal_pm_notify(struct noti
>   	case PM_POST_SUSPEND:
>   		mutex_lock(&thermal_list_lock);
>   
> -		list_for_each_entry(tz, &thermal_tz_list, node) {
> -			mutex_lock(&tz->lock);
> -
> -			cancel_delayed_work(&tz->poll_queue);
> -
> -			reinit_completion(&tz->resume);
> -			tz->resuming = true;
> -
> -			/*
> -			 * Replace the work function with the resume one, which
> -			 * will restore the original work function and schedule
> -			 * the polling work if needed.
> -			 */
> -			INIT_DELAYED_WORK(&tz->poll_queue,
> -					  thermal_zone_device_resume);
> -			/* Queue up the work without a delay. */
> -			mod_delayed_work(system_freezable_power_efficient_wq,
> -					 &tz->poll_queue, 0);
> -
> -			mutex_unlock(&tz->lock);
> -		}
> +		list_for_each_entry(tz, &thermal_tz_list, node)
> +			thermal_zone_pm_complete(tz);
>   
>   		mutex_unlock(&thermal_list_lock);
>   		break;
> 
> 
> 

Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>

  reply	other threads:[~2024-10-21 22:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 19:01 [PATCH v2 00/12] thermal: core: Fixes and cleanups, mostly related to thermal zone init and exit Rafael J. Wysocki
2024-10-04 19:05 ` [PATCH v2 01/12] thermal: core: Initialize thermal zones before registering them Rafael J. Wysocki
2024-10-21 22:16   ` Lukasz Luba
2024-10-04 19:09 ` [PATCH v2 02/12] thermal: core: Rearrange PM notification code Rafael J. Wysocki
2024-10-21 22:18   ` Lukasz Luba [this message]
2024-10-04 19:11 ` [PATCH v2 03/12] thermal: core: Represent suspend-related thermal zone flags as bits Rafael J. Wysocki
2024-10-21 22:23   ` Lukasz Luba
2024-10-04 19:15 ` [PATCH v2 04/12] thermal: core: Mark thermal zones as initializing to start with Rafael J. Wysocki
2024-10-21 22:26   ` Lukasz Luba
2024-10-04 19:19 ` [PATCH v2 05/12] thermal: core: Fix race between zone registration and system suspend Rafael J. Wysocki
2024-10-21 22:27   ` Lukasz Luba
2024-10-04 19:23 ` [PATCH v2 06/12] thermal: core: Consolidate thermal zone locking during initialization Rafael J. Wysocki
2024-10-21 22:30   ` Lukasz Luba
2024-10-04 19:26 ` [PATCH v2 07/12] thermal: core: Mark thermal zones as exiting before unregistration Rafael J. Wysocki
2024-10-21 22:31   ` Lukasz Luba
2024-10-04 19:30 ` [PATCH v2 08/12] thermal: core: Consolidate thermal zone locking in the exit path Rafael J. Wysocki
2024-10-21 22:33   ` Lukasz Luba
2024-10-04 19:33 ` [PATCH v2 09/12] thermal: core: Update thermal zones after cooling device binding Rafael J. Wysocki
2024-10-21 22:35   ` Lukasz Luba
2024-10-04 19:35 ` [PATCH v2 10/12] thermal: core: Drop need_update field from struct thermal_zone_device Rafael J. Wysocki
2024-10-21 22:36   ` Lukasz Luba
2024-10-04 19:39 ` [PATCH v2 11/12] thermal: core: Move lists of thermal instances to trip descriptors Rafael J. Wysocki
2024-10-21 22:44   ` Lukasz Luba
2024-10-04 19:42 ` [PATCH v2 12/12] thermal: core: Pass trip descriptors to trip bind/unbind functions Rafael J. Wysocki
2024-10-21 22:37   ` Lukasz Luba
2024-10-11 18:50 ` [PATCH v2 00/12] thermal: core: Fixes and cleanups, mostly related to thermal zone init and exit Rafael J. Wysocki
2024-10-21 11:05   ` Rafael J. Wysocki
2024-10-21 22:45     ` Lukasz Luba
2024-10-22  9:56       ` Rafael J. Wysocki

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=24c31077-8970-4fcd-bcaa-60d1a3da8f27@arm.com \
    --to=lukasz.luba@arm.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=srinivas.pandruvada@linux.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

all inboxes | Powered by JetHome®