Even though the previous binding made it a required child node, the
implementation in Linux never made it mandatory and just ignored thermal
zones without trip points.
This was even effectively encouraged, since the thermal core wouldn't
allow a thermal sensor to probe without a thermal zone.
In the case where you had a thermal device that had multiple sensors but
with enough knowledge to provide trip points for only a few of them,
this meant that the only way to make that driver probe was to provide a
thermal zone without the trips node required by the binding.
This obviously led to a fair number of device trees doing exactly that,
making the initial binding requirement ineffective.
Let's make it clear by dropping that requirement.
Cc: Amit Kucheria <am...@kernel.org>
Cc: Daniel Lezcano <daniel.lezc...@linaro.org>
Cc: linux...@vger.kernel.org
Cc: Zhang Rui <rui.zh...@intel.com>
Signed-off-by: Maxime Ripard <max...@cerno.tech>
---
Documentation/devicetree/bindings/thermal/thermal-zones.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
b/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
index 164f71598c59..a07de5ed0ca6 100644
--- a/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
+++ b/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
@@ -215,7 +215,7 @@ patternProperties:
- polling-delay
- polling-delay-passive
- thermal-sensors
- - trips
+
additionalProperties: false
additionalProperties: false
--
2.31.1
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to linux-sunxi+unsubscr...@googlegroups.com.
To view this discussion on the web, visit
https://groups.google.com/d/msgid/linux-sunxi/20210721140424.725744-34-maxime%40cerno.tech.
