[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gze1wBEMcuEu4Aa9343rh-3=Bu+pdSYuY3stMd8QGf0A@mail.gmail.com>
Date: Fri, 24 Mar 2023 14:19:58 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Zhang Rui <rui.zhang@...el.com>
Cc: linux-pm@...r.kernel.org, rafael.j.wysocki@...el.com,
daniel.lezcano@...aro.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/5] thermal/core: Reset cooling state during cooling
device unregistration
On Fri, Mar 24, 2023 at 8:08 AM Zhang Rui <rui.zhang@...el.com> wrote:
>
> When unregistering a cooling device, it is possible that the cooling
> device has been activated. And once the cooling device is unregistered,
> no one will deactivate it anymore.
>
> Reset cooling state during cooling device unregistration.
>
> Signed-off-by: Zhang Rui <rui.zhang@...el.com>
> ---
> In theory, this problem that this patch fixes can be triggered on a
> platform with ACPI Active cooling, by
> 1. overheat the system to trigger ACPI active cooling
> 2. unload ACPI fan driver
> 3. check if the fan is still spinning
> But I don't have such a system so I didn't trigger then problem and I
> only did build & boot test.
So I'm not sure if this change is actually safe.
In the example above, the system will still need the fan to spin after
the ACPI fan driver is unloaded in order to cool down, won't it?
> ---
> drivers/thermal/thermal_core.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
> index 30ff39154598..fd54e6c10b60 100644
> --- a/drivers/thermal/thermal_core.c
> +++ b/drivers/thermal/thermal_core.c
> @@ -1192,6 +1192,10 @@ void thermal_cooling_device_unregister(struct thermal_cooling_device *cdev)
> }
> }
>
> + mutex_lock(&cdev->lock);
> + cdev->ops->set_cur_state(cdev, 0);
> + mutex_unlock(&cdev->lock);
> +
> mutex_unlock(&thermal_list_lock);
>
> device_unregister(&cdev->device);
> --
> 2.25.1
>
Powered by blists - more mailing lists