From: Thierry Reding <treding@xxxxxxxxxx>
Each throttling configuration needs to specify the temperature threshold
at which it should start throttling. Previously this was tied to a given
trip point as a cooling device and used the temperature specified for
that trip point. This doesn't work well because the throttling mechanism
is not a cooling device in the traditional sense.
Instead, allow device trees to specify the throttle temperature in the
throttle configuration directly so that the throttle doesn't need to be
exposed as a cooling device.
Signed-off-by: Thierry Reding <treding@xxxxxxxxxx>
---
Changes in v2:
- rename temperature to temperature-millicelsius and drop $ref
- add hysteresis-millicelsius property
.../bindings/thermal/nvidia,tegra124-soctherm.yaml | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.yaml b/Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.yaml
index 04a2ba1aa946..0eb6277082fe 100644
--- a/Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.yaml
+++ b/Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.yaml
@@ -121,6 +121,20 @@ properties:
# high (85%, TEGRA_SOCTHERM_THROT_LEVEL_HIGH)
- 3
+ temperature-millicelsius:
+ minimum: -273000
+ maximum: 200000
+ description: The temperature threshold (in millicelsius) that,
+ when crossed, will trigger the configured automatic throttling.
+
+ hysteresis-millicelsius:
+ description: An unsigned integer expressing the hysteresis delta
+ (in millicelsius) with respect to the threshold temperature
+ property above. Throttling will be initiated when the
+ temperature falls below (temperature - hysteresis). This avoids
+ situations where throttling is repeatedly initiated and stopped
+ because of minor temperature variations.
+
# optional
# Tegra210 specific and valid only for OCx throttle events
nvidia,count-threshold:
--
2.42.0
