Devicetree
 help / color / mirror / Atom feed
From: Lukasz Luba <lukasz.luba@arm.com>
To: Steve Twiss <stwiss.opensource@diasemi.com>,
	Eduardo Valentin <edubezval@gmail.com>,
	LINUX-KERNEL <linux-kernel@vger.kernel.org>,
	LINUX-PM <linux-pm@vger.kernel.org>,
	Zhang Rui <rui.zhang@intel.com>
Cc: DEVICETREE <devicetree@vger.kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Guenter Roeck <linux@roeck-us.net>,
	LINUX-INPUT <linux-input@vger.kernel.org>,
	LINUX-WATCHDOG <linux-watchdog@vger.kernel.org>,
	Lee Jones <lee.jones@linaro.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	Support Opensource <support.opensource@diasemi.com>,
	Wim Van Sebroeck <wim@iguana.be>
Subject: Re: [PATCH V4 7/8] thermal: da9062/61: Thermal junction temperature monitoring driver
Date: Tue, 15 Nov 2016 09:46:51 +0000	[thread overview]
Message-ID: <b2d2809e-b71e-5db0-2aeb-4773dc58960d@arm.com> (raw)
In-Reply-To: <5d6cf6b51d71d2069db20ee427a92271015c337a.1479111766.git.stwiss.opensource@diasemi.com>

On 14/11/16 08:22, Steve Twiss wrote:
> From: Steve Twiss <stwiss.opensource@diasemi.com>
>
> Add junction temperature monitoring supervisor device driver, compatible
> with the DA9062 and DA9061 PMICs. A MODULE_DEVICE_TABLE() macro is added.
>
> If the PMIC's internal junction temperature rises above TEMP_WARN (125
> degC) an interrupt is issued. This TEMP_WARN level is defined as the
> THERMAL_TRIP_HOT trip-wire inside the device driver.
>
> The thermal triggering mechanism is interrupt based and happens when the
> temperature rises above a given threshold level. The component cannot
> return an exact temperature, it only has knowledge if the temperature is
> above or below a given threshold value. A status bit must be polled to
> detect when the temperature falls below that threshold level again. A
> kernel work queue is configured to repeatedly poll and detect when the
> temperature falls below this trip-wire, between 1 and 10 second intervals
> (defaulting at 3 seconds).
>
> This first level of temperature supervision is intended for non-invasive
> temperature control, where the necessary measures for cooling the system
> down are left to the host software.
>
> Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>
>
Looks good to me.

Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>

Regards,
Lukasz

      reply	other threads:[~2016-11-15  9:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14  8:22 [PATCH V4 0/8] da9061: DA9061 driver submission Steve Twiss
2016-11-14  8:22 ` [PATCH V4 1/8] Documentation: devicetree: watchdog: da9062/61 watchdog timer binding Steve Twiss
2016-11-14  8:22 ` [PATCH V4 2/8] Documentation: devicetree: thermal: da9062/61 TJUNC temperature binding Steve Twiss
2016-11-14  8:22 ` [PATCH V4 3/8] Documentation: devicetree: mfd: da9062/61 MFD binding Steve Twiss
2016-11-14  8:22 ` [PATCH V4 4/8] mfd: da9061: MFD core support Steve Twiss
     [not found] ` <cover.1479111766.git.stwiss.opensource-WBD+wuPFNBhBDgjK7y7TUQ@public.gmane.org>
2016-11-14  8:22   ` [PATCH V4 5/8] regulator: da9061: BUCK and LDO regulator driver Steve Twiss
2016-11-14  8:22 ` [PATCH V4 6/8] watchdog: da9062/61: watchdog driver Steve Twiss
2016-11-14  8:22 ` [PATCH V4 8/8] MAINTAINERS: da9062/61 updates to the Dialog Semiconductor search terms Steve Twiss
2016-11-14  8:22 ` [PATCH V4 7/8] thermal: da9062/61: Thermal junction temperature monitoring driver Steve Twiss
2016-11-15  9:46   ` Lukasz Luba [this message]

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=b2d2809e-b71e-5db0-2aeb-4773dc58960d@arm.com \
    --to=lukasz.luba@arm.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=edubezval@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=stwiss.opensource@diasemi.com \
    --cc=support.opensource@diasemi.com \
    --cc=wim@iguana.be \
    /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