Lines Matching +full:- +full:temperature
19 This how-to focuses on enabling new thermal zone and cooling devices to
27 inputs from thermal zone attributes (the current temperature and trip point
28 temperature) and throttle appropriate devices.
30 - `[0-*]` denotes any positive number starting from 0
31 - `[1-*]` denotes any positive number starting from 1
37 ---------------------------------
49 /sys/class/thermal folder as `thermal_zone[0-*]`. It tries to bind all the
61 thermal zone device call-backs.
68 get the current temperature of the thermal zone.
70 set the trip points window. Whenever the current temperature
72 current temperature are found.
76 - "enabled" means the kernel thermal management is
78 - "disabled" will prevent kernel thermal driver action
86 get the temperature above which the certain trip point
89 set the emulation temperature which helps in debugging
90 different threshold temperature points.
118 pointed by dev->of_node as temperature providers. For the zone
126 dev->of_node.
132 passed back, when a temperature reading is needed.
138 sensor temperature. This is mandatory
141 temperature window. When this window is
145 sensor temperature trend.
147 sensor emulated temperature.
150 The thermal zone temperature is provided by the get_temp() function
207 drivers for temperature calculations.
215 drivers for temperature calculations.
218 ------------------------------------
228 to /sys/class/thermal/ folder as `cooling_device[0-*]`. It tries to bind itself
236 thermal cooling devices call-backs.
255 -----------------------------------------------------------------------------
305 ---------------------------
334 array consisting of tuples <lower-state upper-state> of
380 /sys/class/thermal/thermal_zone[0-*]:
381 |---type: Type of the thermal zone
382 |---temp: Current temperature
383 |---mode: Working mode of the thermal zone
384 |---policy: Thermal governor used for this zone
385 |---available_policies: Available thermal governors for this zone
386 |---trip_point_[0-*]_temp: Trip point temperature
387 |---trip_point_[0-*]_type: Trip point type
388 |---trip_point_[0-*]_hyst: Hysteresis value for this trip point
389 |---emul_temp: Emulated temperature set node
390 |---sustainable_power: Sustainable dissipatable power
391 |---k_po: Proportional term during temperature overshoot
392 |---k_pu: Proportional term during temperature undershoot
393 |---k_i: PID's integral term in the power allocator gov
394 |---k_d: PID's derivative term in the power allocator
395 |---integral_cutoff: Offset above which errors are accumulated
396 |---slope: Slope constant applied as linear extrapolation
397 |---offset: Offset constant applied as linear extrapolation
401 /sys/class/thermal/cooling_device[0-*]:
402 |---type: Type of the cooling device(processor/fan/...)
403 |---max_state: Maximum cooling state of the cooling device
404 |---cur_state: Current cooling state of the cooling device
405 |---stats: Directory containing cooling device's statistics
406 |---stats/reset: Writing any value resets the statistics
407 |---stats/time_in_state_ms: Time (msec) spent in various cooling states
408 |---stats/total_trans: Total number of times cooling state is changed
409 |---stats/trans_table: Cooing state transition table
419 /sys/class/thermal/thermal_zone[0-*]:
420 |---cdev[0-*]: [0-*]th cooling device in current thermal zone
421 |---cdev[0-*]_trip_point: Trip point that cdev[0-*] is associated with
422 |---cdev[0-*]_weight: Influence of the cooling device in
433 /sys/class/hwmon/hwmon[0-*]:
434 |---name: The type of the thermal zone devices
435 |---temp[1-*]_input: The current temperature of thermal zone [1-*]
436 |---temp[1-*]_critical: The critical trip point of thermal zone [1-*]
438 Please read Documentation/hwmon/sysfs-interface.rst for additional information.
441 -----------------------
452 Current temperature as reported by thermal zone (sensor).
481 `trip_point_[0-*]_temp`
482 The temperature above which trip point will be fired.
488 `trip_point_[0-*]_type`
491 E.g. it can be one of critical, hot, passive, `active[0-*]` for ACPI
496 `trip_point_[0-*]_hyst`
501 `cdev[0-*]`
507 `cdev[0-*]_trip_point`
508 The trip point in this thermal zone which `cdev[0-*]` is associated
509 with; -1 means the cooling device is not associated with any trip
514 `cdev[0-*]_weight`
515 The influence of `cdev[0-*]` in this thermal zone. This value
526 and can be set to a temperature (in millidegrees) to enable a
537 Interface to set the emulated temperature method in thermal zone
538 (sensor). After setting this temperature, the thermal zone may pass
539 this temperature to platform emulation function if registered or
540 cache it locally. This is useful in debugging different temperature
550 flooding this sysfs node with low temperature values.
555 more information see Documentation/driver-api/thermal/power_allocator.rst
563 controller during temperature overshoot. Temperature overshoot
564 is when the current temperature is above the "desired
565 temperature" trip point. For more information see
566 Documentation/driver-api/thermal/power_allocator.rst
572 controller during temperature undershoot. Temperature undershoot
573 is when the current temperature is below the "desired
574 temperature" trip point. For more information see
575 Documentation/driver-api/thermal/power_allocator.rst
583 Documentation/driver-api/thermal/power_allocator.rst
590 Documentation/driver-api/thermal/power_allocator.rst
595 Temperature offset from the desired temperature trip point
599 accumulates error when temperature is above the desired
600 temperature trip point. For more information see
601 Documentation/driver-api/thermal/power_allocator.rst
609 to determine a hotspot temperature based off the sensor's
617 to determine a hotspot temperature based off the sensor's
624 -------------------------
629 - for generic ACPI: should be "Fan", "Processor" or "LCD"
630 - for memory controller device on intel_menlow platform:
644 - cur_state == 0 means no cooling
645 - cur_state == max_state means the maximum cooling.
673 reading this will return an -EFBIG error.
692 |---type: acpitz
693 |---temp: 37000
694 |---mode: enabled
695 |---policy: step_wise
696 |---available_policies: step_wise fair_share
697 |---trip_point_0_temp: 100000
698 |---trip_point_0_type: critical
699 |---trip_point_1_temp: 80000
700 |---trip_point_1_type: passive
701 |---trip_point_2_temp: 70000
702 |---trip_point_2_type: active0
703 |---trip_point_3_temp: 60000
704 |---trip_point_3_type: active1
705 |---cdev0: --->/sys/class/thermal/cooling_device0
706 |---cdev0_trip_point: 1 /* cdev0 can be used for passive */
707 |---cdev0_weight: 1024
708 |---cdev1: --->/sys/class/thermal/cooling_device3
709 |---cdev1_trip_point: 2 /* cdev1 can be used for active[0]*/
710 |---cdev1_weight: 1024
713 |---type: Processor
714 |---max_state: 8
715 |---cur_state: 0
718 |---type: Fan
719 |---max_state: 2
720 |---cur_state: 0
724 |---name: acpitz
725 |---temp1_input: 37000
726 |---temp1_crit: 100000
732 -----------------
735 of temperature of the thermal zone. Ideally, the thermal sensor drivers
738 temperature values.
741 -------------------------
748 -----------------------------
758 ------------------------
767 On an event of critical trip temperature crossing. Thermal framework
772 queue to fire after a pre-determined number of seconds to start
783 profiled non-zero positive value is a must for emergerncy poweroff to be