[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240724153108.914704-1-m.majewski2@samsung.com>
Date: Wed, 24 Jul 2024 17:31:05 +0200
From: Mateusz Majewski <m.majewski2@...sung.com>
To: Rob Herring <robh@...nel.org>
Cc: Mateusz Majewski <m.majewski2@...sung.com>, linux-pm@...r.kernel.org,
linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Bartlomiej Zolnierkiewicz <bzolnier@...il.com>, Krzysztof Kozlowski
<krzk@...nel.org>, "Rafael J. Wysocki" <rafael@...nel.org>, Daniel Lezcano
<daniel.lezcano@...aro.org>, Zhang Rui <rui.zhang@...el.com>, Lukasz Luba
<lukasz.luba@....com>, Conor Dooley <conor+dt@...nel.org>, Alim Akhtar
<alim.akhtar@...sung.com>, Sam Protsenko <semen.protsenko@...aro.org>
Subject: Re: [PATCH 6/6] dt-bindings: thermal: samsung,exynos: remove
outdated information on trip point count
> If the old text had nothing to do with the h/w, then I suppose so. I
> would have assumed the h/w supports some number of thresholds causing
> some action whether an interrupt or some sort of shutdown.
That is true, but after the mentioned change only 3 are used at the
time: one lower than current temperature, one higher than current
temperature, and one for the critical temperature. So, from the
perspective of somebody writing the devicetree source file this limit is
probably irrelevant?
Powered by blists - more mailing lists