From: Wei Ni <wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Eduardo Valentin <edubezval-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
MLongnecker-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org,
mikko.perttunen-/1wQRMveznE@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V7 08/12] of: add notes of critical trips for soctherm
Date: Tue, 15 Mar 2016 15:49:27 +0800 [thread overview]
Message-ID: <56E7BE87.405@nvidia.com> (raw)
In-Reply-To: <20160314210027.GA4740-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
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-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>> Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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.
>
> * Unknown Key
> * 0x7DA4E256
>
WARNING: multiple messages have this Message-ID (diff)
From: Wei Ni <wni@nvidia.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: <rui.zhang@intel.com>, <thierry.reding@gmail.com>,
<MLongnecker@nvidia.com>, <swarren@wwwdotorg.org>,
<mikko.perttunen@kapsi.fi>, <linux-tegra@vger.kernel.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V7 08/12] of: add notes of critical trips for soctherm
Date: Tue, 15 Mar 2016 15:49:27 +0800 [thread overview]
Message-ID: <56E7BE87.405@nvidia.com> (raw)
In-Reply-To: <20160314210027.GA4740@localhost.localdomain>
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@nvidia.com>
>> Acked-by: Rob Herring <robh@kernel.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.
>
> * Unknown Key
> * 0x7DA4E256
>
next prev parent reply other threads:[~2016-03-15 7:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 3:11 [PATCH V7 08/12] of: add notes of critical trips for soctherm Wei Ni
2016-03-11 3:11 ` Wei Ni
2016-03-14 21:00 ` Eduardo Valentin
[not found] ` <20160314210027.GA4740-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2016-03-15 7:49 ` Wei Ni [this message]
2016-03-15 7:49 ` Wei Ni
2016-03-15 8:14 ` Wei Ni
2016-03-15 8:14 ` Wei Ni
[not found] ` <56E7C457.5000301-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-15 19:52 ` Eduardo Valentin
2016-03-15 19:52 ` Eduardo Valentin
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=56E7BE87.405@nvidia.com \
--to=wni-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=MLongnecker-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=edubezval-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mikko.perttunen-/1wQRMveznE@public.gmane.org \
--cc=rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.