path: root/Documentation/driver-api
diff options
authorThara Gopinath <>2021-01-21 21:34:06 -0500
committerDaniel Lezcano <>2021-04-22 13:15:19 +0200
commita5655d90cf508598b5f5bbccd911924cf8dc9060 (patch)
tree4efa39762b83107a9245e3a6b4ac950f282c6aa0 /Documentation/driver-api
parentd60d6e7adfc3814f6de03c978ff1daab21478f87 (diff)
Documentation: driver-api: thermal: Remove thermal_notify_framework from documentation
Since thermal_notify_framework is no longer supported/implemented remove the entry from sysfs-api.rst. Signed-off-by: Thara Gopinath <> Signed-off-by: Daniel Lezcano <> Link:
Diffstat (limited to 'Documentation/driver-api')
1 files changed, 1 insertions, 11 deletions
diff --git a/Documentation/driver-api/thermal/sysfs-api.rst b/Documentation/driver-api/thermal/sysfs-api.rst
index 29fdd817ddb0..4b638c14bc16 100644
--- a/Documentation/driver-api/thermal/sysfs-api.rst
+++ b/Documentation/driver-api/thermal/sysfs-api.rst
@@ -730,17 +730,7 @@ This function returns the thermal_instance corresponding to a given
{thermal_zone, cooling_device, trip_point} combination. Returns NULL
if such an instance does not exist.
-4.3. thermal_notify_framework
-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.
-4.4. thermal_cdev_update
+4.3. thermal_cdev_update
This function serves as an arbitrator to set the state of a cooling