devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.guo@linaro.org>
To: "edubezval@gmail.com" <edubezval@gmail.com>
Cc: Anson Huang <b20788@freescale.com>,
	Zhang Rui <rui.zhang@intel.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH V3] Thermal: imx: add i.mx6sx thermal support
Date: Sat, 9 Aug 2014 21:25:47 +0800	[thread overview]
Message-ID: <20140809132544.GA8981@dragon> (raw)
In-Reply-To: <CAC-25o_C1ijr64NyA22JqfS9Z90-v9iseaYzcf1ojy_QNXzExA@mail.gmail.com>

On Fri, Aug 08, 2014 at 08:15:54AM -0400, edubezval@gmail.com wrote:
> Hello Shawn,
> 
> On Thu, Aug 7, 2014 at 4:50 AM, Shawn Guo <shawn.guo@linaro.org> wrote:
> > On Wed, Aug 06, 2014 at 03:12:09PM +0800, Anson Huang wrote:
> >> i.MX6SX has some new features of thermal interrupt function,
> >> there are LOW, HIGH and PANIC irq for thermal sensor, so add
> >> platform data to separate different thermal version;
> >>
> >> The reset value of LOW ALARM is 0 which means the highest
> >> temp, so the LOW ALARM will be triggered once irq is enabled,
> >> so we need to correct it before enabling thermal irq;
> >>
> >> Enable PANIC ALARM as critical trip point, it will trigger
> >> system reset via SRC module once PANIC IRQ is triggered, it
> >> is pure hardware function, so use it instead of software
> >> reset by cooling device.
> >>
> >> Signed-off-by: Anson Huang <b20788@freescale.com>
> >
> > Tested-by: Shawn Guo <shawn.guo@linaro.org>
> 
> Thanks!
> 
> Did you have the chance to test on both? i.MX6Q and i.MX6SX?

Yes, I did test on both i.MX6Q and i.MX6SX.

Shawn

  reply	other threads:[~2014-08-09 13:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06  7:12 [PATCH V3] Thermal: imx: add i.mx6sx thermal support Anson Huang
     [not found] ` <1407309129-5562-1-git-send-email-b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-08-06 13:24   ` edubezval-Re5JQEeQqe8AvxtiuMwx3w
2014-08-06 13:56     ` Anson.Huang
2014-08-07  8:50   ` Shawn Guo
2014-08-08 12:15     ` edubezval-Re5JQEeQqe8AvxtiuMwx3w
2014-08-09 13:25       ` Shawn Guo [this message]
2014-08-09 14:29   ` 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=20140809132544.GA8981@dragon \
    --to=shawn.guo@linaro.org \
    --cc=b20788@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).