From: Wei Ni <wni@nvidia.com>
To: Rob Herring <robh@kernel.org>
Cc: thierry.reding@gmail.com, daniel.lezcano@linaro.org,
edubezval@gmail.com, linux-tegra@vger.kernel.org,
rui.zhang@intel.com, srikars@nvidia.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v1 01/12] of: Add bindings of thermtrip for Tegra soctherm
Date: Fri, 28 Dec 2018 11:28:42 +0800 [thread overview]
Message-ID: <1441d2d1-acfa-7b8d-5ed8-c2ca257df05d@nvidia.com> (raw)
In-Reply-To: <20181227230630.GA3659@bogus>
On 28/12/2018 7:06 AM, Rob Herring wrote:
> On Tue, Dec 18, 2018 at 03:34:33PM +0800, Wei Ni wrote:
>> Add optional property "nvidia,thermtrips".
>> If present, these trips will be used as HW shutdown trips,
>> and critical trips will be used as SW shutdown trips.
>>
>> Signed-off-by: Wei Ni <wni@nvidia.com>
>> ---
>> .../bindings/thermal/nvidia,tegra124-soctherm.txt | 20 +++++++++++++++++---
>> 1 file changed, 17 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.txt b/Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.txt
>> index b6c0ae53d4dc..ab66d6feab4b 100644
>> --- a/Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.txt
>> +++ b/Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.txt
>> @@ -55,10 +55,21 @@ Required properties :
>> - #cooling-cells: Should be 1. This cooling device only support on/off state.
>> See ./thermal.txt for a description of this property.
>>
>> +Optional properties:
>> +- nvidia,thermtrips : When present, this property specifies the temperature at
>> + which the soctherm hardware will assert the thermal trigger signal to the
>> + Power Management IC, which can be configured to reset or shutdown the device.
>> + It is an array of pairs where each pair represents a tsensor id followed by a
>> + temperature in milli Celcius. In the absence of this property the critical
>> + trip point will be used for thermtrip temperature.
>> +
>> Note:
>> -- the "critical" type trip points will be set to SOC_THERM hardware as the
>> -shut down temperature. Once the temperature of this thermal zone is higher
>> -than it, the system will be shutdown or reset by hardware.
>> +- the "critical" type trip points will be used to set the temperature at which
>> +the SOC_THERM hardware will assert a thermal trigger if the "nvidia,thermtrips"
>> +property is missing. When the thermtrips property is present, the breach of a
>> +critical trip point is reported back to the thermal framework to implement
>> +software shutdown.
>
> This hardly seems like a NVidia specific concept. A h/w shutdown
> temperature... Come up with something common.
Hi Rob,
In current thermal framework, it doesn't support to set h/w shutdown
trips, the "critical" trip is used for s/w shutdown. I noticed that in
rockchip-thermal driver, it also used "rockchip,hw-tshut-temp" to set
h/w shutdown temperature.
>
> Also, we already have a temperature table. Why do we need temperatures
> in 2 places.
Sorry, what do you mean temperature table? Do you mean the trip nodes?
Thanks.
Wei.
>
>> +
>> - the "hot" type trip points will be set to SOC_THERM hardware as the throttle
>> temperature. Once the the temperature of this thermal zone is higher
>> than it, it will trigger the HW throttle event.
>> @@ -79,6 +90,9 @@ Example :
>>
>> #thermal-sensor-cells = <1>;
>>
>> + nvidia,thermtrips = <TEGRA124_SOCTHERM_SENSOR_CPU 102500
>> + TEGRA124_SOCTHERM_SENSOR_GPU 103000>;
>> +
>> throttle-cfgs {
>> /*
>> * When the "heavy" cooling device triggered,
>> --
>> 2.7.4
>>
next prev parent reply other threads:[~2018-12-28 3:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 7:34 [PATCH v1 00/12] Add some functionalities for Tegra soctherm Wei Ni
2018-12-18 7:34 ` Wei Ni
2019-01-21 9:26 ` Wei Ni
2018-12-18 7:34 ` [PATCH v1 01/12] of: Add bindings of thermtrip " Wei Ni
2018-12-27 23:06 ` Rob Herring
2018-12-28 3:28 ` Wei Ni [this message]
2019-02-20 1:22 ` Eduardo Valentin
2019-02-20 8:39 ` Wei Ni
2018-12-18 7:34 ` [PATCH v1 02/12] thermal: tegra: support hw and sw shutdown Wei Ni
2018-12-18 7:34 ` [PATCH v1 03/12] arm64: dts: tegra210: set thermtrip Wei Ni
2018-12-18 7:34 ` [PATCH v1 04/12] of: Add bindings of gpu hw throttle for Tegra soctherm Wei Ni
2019-02-18 20:29 ` Rob Herring
2019-02-19 6:08 ` Wei Ni
2019-02-18 20:33 ` Rob Herring
2019-02-19 6:34 ` Wei Ni
2018-12-18 7:34 ` [PATCH v1 05/12] thermal: tegra: add support for gpu hw-throttle Wei Ni
2018-12-18 7:34 ` [PATCH v1 06/12] arm64: dts: tegra210: set gpu hw throttle level Wei Ni
2018-12-18 7:34 ` [PATCH v1 07/12] thermal: tegra: add support for thermal IRQ Wei Ni
2018-12-18 7:34 ` [PATCH v1 08/12] thermal: tegra: add set_trips functionality Wei Ni
2018-12-18 7:34 ` [PATCH v1 09/12] thermal: tegra: add support for EDP IRQ Wei Ni
2018-12-18 7:34 ` [PATCH v1 10/12] arm64: dts: tegra210: set EDP interrupt line Wei Ni
2018-12-18 7:34 ` [PATCH v1 11/12] of: Add bindings of OC hw throttle for Tegra soctherm Wei Ni
2019-02-18 20:32 ` Rob Herring
2019-02-19 6:31 ` Wei Ni
2018-12-18 7:34 ` [PATCH v1 12/12] thermal: tegra: enable OC hw throttle Wei Ni
2018-12-18 7:50 ` [PATCH v1 00/12] Add some functionalities for Tegra soctherm Wei Ni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1441d2d1-acfa-7b8d-5ed8-c2ca257df05d@nvidia.com \
--to=wni@nvidia.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=srikars@nvidia.com \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox