[thermal:,thermal/next] Documentation: driver-api: thermal: Remove thermal_notify_framework from documentation

Message ID 161955266951.29796.17603412725978656311.tip-bot2@tip-bot2
State New
Headers show
  • [thermal:,thermal/next] Documentation: driver-api: thermal: Remove thermal_notify_framework from documentation
Related show

Commit Message

tip-bot2 for Thomas Gleixner April 27, 2021, 7:44 p.m.
The following commit has been merged into the thermal/next branch of thermal:

Commit-ID:     a5655d90cf508598b5f5bbccd911924cf8dc9060
Gitweb:        https://git.kernel.org/pub/scm/linux/kernel/git/thermal/linux.git//a5655d90cf508598b5f5bbccd911924cf8dc9060
Author:        Thara Gopinath <thara.gopinath@linaro.org>
AuthorDate:    Thu, 21 Jan 2021 21:34:06 -05:00
Committer:     Daniel Lezcano <daniel.lezcano@linaro.org>
CommitterDate: Thu, 22 Apr 2021 13:15:19 +02:00

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 <thara.gopinath@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20210122023406.3500424-4-thara.gopinath@linaro.org
 Documentation/driver-api/thermal/sysfs-api.rst | 12 +-----------
 1 file changed, 1 insertion(+), 11 deletions(-)


diff --git a/Documentation/driver-api/thermal/sysfs-api.rst b/Documentation/driver-api/thermal/sysfs-api.rst
index 29fdd81..4b638c1 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