[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <8409966.T7Z3S40VBb@kreacher>
Date: Mon, 17 Jun 2024 19:41:25 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Linux PM <linux-pm@...r.kernel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rafael@...nel.org>, Lukasz Luba <lukasz.luba@....com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Zhang Rui <rui.zhang@...el.com>, Shawn Guo <shawnguo@...nel.org>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Thara Gopinath <thara.gopinath@...il.com>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>, linux-wireless@...r.kernel.org,
linux-tegra@...r.kernel.org
Subject:
[PATCH v1 00/14] thermal: Eliminate trip IDs from thermal driver interface
Hi Everyone,
Trip IDs, which should be internal to the thermal core, are still used in the
thermal driver interface in some places, but fortunately it does not take too
much effort to get rid of them.
First of all, the .set_trip_temp() zone callback uses a trip ID as one of its
arguments, but this isn't really necessary and there are a few weaknesses
related to doing that. Please see the changelog of patch [04/14] for details.
Apart from that, several drivers use the thermal_zone_get_trip() helper
function for trip point lookup which can be differently. Patches [06-12/14]
address those cases (please see the individual patch changelogs for details).
The remaining patches in the series are preliminary changes or cleanups.
The series is based on the two cleanup series posted previously:
https://lore.kernel.org/linux-pm/5794974.DvuYhMxLoT@kreacher/T/#t
https://lore.kernel.org/linux-pm/12458899.O9o76ZdvQC@kreacher/T/#t
that have been included into the linux-next thermal material.
This series is available from the thermal-core-experimental branch
in linux-pm.git.
Thanks!
Powered by blists - more mailing lists