On Fri, Jul 19, 2024 at 02:08:50PM +0200, Mateusz Majewski wrote:
> This is not true as of commit 5314b1543787 ("thermal/drivers/exynos: Use
> set_trips ops").
>
> Signed-off-by: Mateusz Majewski <m.majewski2@xxxxxxxxxxx>
> ---
> .../bindings/thermal/samsung,exynos-thermal.yaml | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yaml b/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yaml
> index 4363ee625339..5a82764a4dbb 100644
> --- a/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yaml
> +++ b/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yaml
> @@ -40,11 +40,8 @@ properties:
> interrupts:
> description: |
> The Exynos TMU supports generating interrupts when reaching given
> - temperature thresholds. Number of supported thermal trip points depends
> - on the SoC (only first trip points defined in DT will be configured)::
> - - most of SoC: 4
> - - samsung,exynos5433-tmu: 8
> - - samsung,exynos7-tmu: 8
> + temperature thresholds. The trip points will be set dynamically in
> + runtime, which means there is no limit on the number of trip points.
How can the hardware change how many trip points it supports?
> maxItems: 1
>
> reg:
> --
> 2.45.1
>
