diff options
author | Mark Brown <broonie@kernel.org> | 2021-06-23 16:56:31 +0100 |
---|---|---|
committer | Mark Brown <broonie@kernel.org> | 2021-06-23 16:56:31 +0100 |
commit | 7fb593cbd88cf4df01c096d4dc320f027dfa2560 (patch) | |
tree | 1970f6b62728d95ab52de9813bfcf66cd59a48b5 /Documentation/driver-api/thermal/sysfs-api.rst | |
parent | ebad413c3cb04d60bb6b5f2ec4009af52a8761cb (diff) | |
parent | ddf275b219ab22bc07c14ac88c290694089dced0 (diff) |
Merge remote-tracking branch 'regulator/for-5.14' into regulator-next
Diffstat (limited to 'Documentation/driver-api/thermal/sysfs-api.rst')
-rw-r--r-- | Documentation/driver-api/thermal/sysfs-api.rst | 24 |
1 files changed, 9 insertions, 15 deletions
diff --git a/Documentation/driver-api/thermal/sysfs-api.rst b/Documentation/driver-api/thermal/sysfs-api.rst index 4b638c14bc16..c93fa5e961a0 100644 --- a/Documentation/driver-api/thermal/sysfs-api.rst +++ b/Documentation/driver-api/thermal/sysfs-api.rst @@ -740,21 +740,15 @@ possible. 5. thermal_emergency_poweroff ============================= -On an event of critical trip temperature crossing. Thermal framework -allows the system to shutdown gracefully by calling orderly_poweroff(). -In the event of a failure of orderly_poweroff() to shut down the system -we are in danger of keeping the system alive at undesirably high -temperatures. To mitigate this high risk scenario we program a work -queue to fire after a pre-determined number of seconds to start -an emergency shutdown of the device using the kernel_power_off() -function. In case kernel_power_off() fails then finally -emergency_restart() is called in the worst case. +On an event of critical trip temperature crossing the thermal framework +shuts down the system by calling hw_protection_shutdown(). The +hw_protection_shutdown() first attempts to perform an orderly shutdown +but accepts a delay after which it proceeds doing a forced power-off +or as last resort an emergency_restart. The delay should be carefully profiled so as to give adequate time for -orderly_poweroff(). In case of failure of an orderly_poweroff() the -emergency poweroff kicks in after the delay has elapsed and shuts down -the system. +orderly poweroff. -If set to 0 emergency poweroff will not be supported. So a carefully -profiled non-zero positive value is a must for emergency poweroff to be -triggered. +If the delay is set to 0 emergency poweroff will not be supported. So a +carefully profiled non-zero positive value is a must for emergency +poweroff to be triggered. |