The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Lukasz Luba <lukasz.luba@arm.com>
To: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
Cc: rui.zhang@intel.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, rafael@kernel.org
Subject: Re: [PATCH 2/4] thermal/core: Add dedicated release callback for thermal zones
Date: Wed, 13 May 2026 16:02:50 +0100	[thread overview]
Message-ID: <cdbc4fa5-53cb-4288-a3d6-6c53fce1c290@arm.com> (raw)
In-Reply-To: <20260508180511.1306659-3-daniel.lezcano@oss.qualcomm.com>



On 5/8/26 19:05, Daniel Lezcano wrote:
> The thermal class release callback currently handles thermal zone
> cleanup by checking the device name prefix.
> 
> Move the thermal zone cleanup to a dedicated struct device release
> callback.  This avoids relying on device names to select the release
> path and keeps the thermal zone lifetime handling local to the thermal
> zone object.
> 
> Signed-off-by: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
> ---
>   drivers/thermal/thermal_core.c | 28 ++++++++++++----------------
>   1 file changed, 12 insertions(+), 16 deletions(-)
> 
> diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
> index cf5d4a9c11fe..a79fc4cdb078 100644
> --- a/drivers/thermal/thermal_core.c
> +++ b/drivers/thermal/thermal_core.c
> @@ -949,24 +949,8 @@ static void thermal_unbind_cdev_from_trip(struct thermal_zone_device *tz,
>   	kfree(pos);
>   }
>   
> -static void thermal_release(struct device *dev)
> -{
> -	struct thermal_zone_device *tz;
> -
> -	if (!strncmp(dev_name(dev), "thermal_zone",
> -		     sizeof("thermal_zone") - 1)) {
> -		tz = to_thermal_zone(dev);
> -		thermal_zone_destroy_device_groups(tz);
> -		thermal_set_governor(tz, NULL);
> -		ida_destroy(&tz->ida);
> -		mutex_destroy(&tz->lock);
> -		complete(&tz->removal);
> -	}
> -}
> -
>   static const struct class thermal_class = {
>   	.name = "thermal",
> -	.dev_release = thermal_release,
>   };
>   static bool thermal_class_unavailable __ro_after_init = true;
>   
> @@ -1473,6 +1457,17 @@ static void thermal_zone_init_complete(struct thermal_zone_device *tz)
>   	__thermal_zone_device_update(tz, THERMAL_EVENT_UNSPECIFIED);
>   }
>   
> +static void thermal_zone_device_release(struct device *dev)
> +{
> +	struct thermal_zone_device *tz = to_thermal_zone(dev);
> +
> +	thermal_zone_destroy_device_groups(tz);
> +	thermal_set_governor(tz, NULL);
> +	ida_destroy(&tz->ida);
> +	mutex_destroy(&tz->lock);
> +	complete(&tz->removal);
> +}
> +
>   /**
>    * thermal_zone_device_register_with_trips() - register a new thermal zone device
>    * @type:	the thermal zone device type
> @@ -1580,6 +1575,7 @@ thermal_zone_device_register_with_trips(const char *type,
>   		tz->ops.critical = thermal_zone_device_critical;
>   
>   	tz->device.class = &thermal_class;
> +	tz->device.release = thermal_zone_device_release;
>   	tz->devdata = devdata;
>   	tz->num_trips = num_trips;
>   	for_each_trip_desc(tz, td) {

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

  reply	other threads:[~2026-05-13 15:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 18:05 [PATCH 0/4] thermal/core: Decouple release paths for tz and cdev Daniel Lezcano
2026-05-08 18:05 ` [PATCH 1/4] thermal/core: Add dedicated release callback for cooling devices Daniel Lezcano
2026-05-13 15:02   ` Lukasz Luba
2026-05-08 18:05 ` [PATCH 2/4] thermal/core: Add dedicated release callback for thermal zones Daniel Lezcano
2026-05-13 15:02   ` Lukasz Luba [this message]
2026-05-08 18:05 ` [PATCH 3/4] thermal/core: Allocate the thermal class dynamically Daniel Lezcano
2026-05-08 18:24   ` Rafael J. Wysocki
2026-05-08 19:22     ` Daniel Lezcano
2026-05-08 19:26       ` Rafael J. Wysocki
2026-05-08 19:28         ` Daniel Lezcano
2026-05-13 15:03   ` Lukasz Luba
2026-05-08 18:05 ` [PATCH 4/4] thermal/core: Use the thermal class pointer as init guard Daniel Lezcano
2026-05-13 15:03   ` Lukasz Luba
2026-05-08 18:10 ` [PATCH 0/4] thermal/core: Decouple release paths for tz and cdev Daniel Lezcano
2026-05-13 14:22   ` Daniel Lezcano
2026-05-13 15:06     ` Rafael J. Wysocki
2026-05-13 15:45       ` Lukasz Luba
2026-05-13 15:48         ` Daniel Lezcano

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=cdbc4fa5-53cb-4288-a3d6-6c53fce1c290@arm.com \
    --to=lukasz.luba@arm.com \
    --cc=daniel.lezcano@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --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