On Fri, Jul 26, 2024 at 01:01:10PM +0200, Mateusz Majewski wrote:
> This is not true as of commit 5314b1543787 ("thermal/drivers/exynos: Use
> set_trips ops").
What is not true?
How can the h/w change? I already asked that. Please make your commit
message summarize prior discussions so that the patch stands on its own
and you don't get the same response again. Assume the reviewers have 0
recollection of the prior versions because we don't. This is just one of
100s of patches a week...
>
> Signed-off-by: Mateusz Majewski <m.majewski2@xxxxxxxxxxx>
> ---
> v1 -> v2: remove an unnecessary sentence.
>
> .../devicetree/bindings/thermal/samsung,exynos-thermal.yaml | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yaml b/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yaml
> index b8c0bb7f4263..b85b4c420cd3 100644
> --- a/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yaml
> +++ b/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yaml
> @@ -40,11 +40,7 @@ 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.
> maxItems: 1
>
> reg:
> --
> 2.45.1
>
