path: root/drivers/thermal
diff options
authorThara Gopinath <>2021-01-21 21:34:05 -0500
committerDaniel Lezcano <>2021-04-22 13:14:09 +0200
commitd60d6e7adfc3814f6de03c978ff1daab21478f87 (patch)
tree6a11b5580c04cba96359292eedabe46cbe2385cf /drivers/thermal
parent93effd83b6927c0252bb1e35aa3e116d3e2527bb (diff)
thermal/core: Remove thermal_notify_framework
thermal_notify_framework just updates for a single trip point where as thermal_zone_device_update does other bookkeeping like updating the temperature of the thermal zone and setting the next trip point. The only driver that was using thermal_notify_framework was updated in the previous patch to use thermal_zone_device_update instead. Since there are no users for thermal_notify_framework remove it. Signed-off-by: Thara Gopinath <> Signed-off-by: Daniel Lezcano <> Link:
Diffstat (limited to 'drivers/thermal')
1 files changed, 0 insertions, 18 deletions
diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
index 3566fd291399..d20b25f40d19 100644
--- a/drivers/thermal/thermal_core.c
+++ b/drivers/thermal/thermal_core.c
@@ -561,24 +561,6 @@ void thermal_zone_device_update(struct thermal_zone_device *tz,
- * thermal_notify_framework - Sensor drivers use this API to notify framework
- * @tz: thermal zone device
- * @trip: indicates which trip point has been crossed
- *
- * This function handles the trip events from sensor drivers. It starts
- * throttling the cooling devices according to the policy configured.
- * For CRITICAL and HOT trip points, this notifies the respective drivers,
- * and does actual throttling for other trip points i.e ACTIVE and PASSIVE.
- * The throttling policy is based on the configured platform data; if no
- * platform data is provided, this uses the step_wise throttling policy.
- */
-void thermal_notify_framework(struct thermal_zone_device *tz, int trip)
- handle_thermal_trip(tz, trip);
static void thermal_zone_device_check(struct work_struct *work)
struct thermal_zone_device *tz = container_of(work, struct