[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56E7C457.5000301@nvidia.com>
Date: Tue, 15 Mar 2016 16:14:15 +0800
From: Wei Ni <wni@...dia.com>
To: Eduardo Valentin <edubezval@...il.com>
CC: <rui.zhang@...el.com>, <thierry.reding@...il.com>,
<MLongnecker@...dia.com>, <swarren@...dotorg.org>,
<mikko.perttunen@...si.fi>, <linux-tegra@...r.kernel.org>,
<linux-pm@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V7 08/12] of: add notes of critical trips for soctherm
On 2016年03月15日 15:49, Wei Ni wrote:
>
>
> On 2016年03月15日 05:00, Eduardo Valentin wrote:
>> * PGP Signed by an unknown key
>>
>> On Fri, Mar 11, 2016 at 11:11:00AM +0800, Wei Ni wrote:
>>> The "critical" type trip in thermal zone can be
>>> set to SOC_THERM hardware, it can trigger shut down
>>> or reset event from hardware.
>>>
>>> Signed-off-by: Wei Ni <wni@...dia.com>
>>> Acked-by: Rob Herring <robh@...nel.org>
>>> ---
>>> Documentation/devicetree/bindings/thermal/tegra-soctherm.txt | 12 ++++++++++++
>>> 1 file changed, 12 insertions(+)
>>
>> I did not see in your patch set an update on the compatible string for
>> the new chip. Did I miss something?
>
> As I said in the previous [00/12], the "commit 193c9d23a0f0" already added the
> compatible string. At that time, it just used current tegra_soctherm.c driver to
> support Tegra210, it can work, but can't show temperatures correctly.
Oh, sorry, I made a mistake, this "commit 193c9d23a0f0" just added the
compatible string, did not use current tegra_soctherm driver to support Tegra210.
Wei.
>
>>
>> * Unknown Key
>> * 0x7DA4E256
>>
Powered by blists - more mailing lists