linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Keerthy <j-keerthy@ti.com>
Cc: rui.zhang@intel.com, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-omap@vger.kernel.org, rk@ti.com,
	t-kristo@ti.com
Subject: Re: [PATCH 0/2] thermal: omap: dra752: Remove TSHUT configuration
Date: Tue, 24 Jan 2017 02:13:02 -0800	[thread overview]
Message-ID: <20170124101300.GA21523@localhost.localdomain> (raw)
In-Reply-To: <560cf909-0303-1827-1f58-c700d785a2b9@ti.com>

On Mon, Jan 23, 2017 at 08:49:29PM +0530, Keerthy wrote:
> Eduardo,
> 
> On Friday 06 January 2017 11:31 AM, Keerthy wrote:
> >Technical Reference Manual [1] mandates that software should
> >not be configuring the thermal shutdown thresholds. Hence
> >removing TSHUT_CONFIG.
> 
> Any comments on this?

I do not see issues on these patches. Queueing for next rc.

> 
> - Keerthy
> >
> >[1] http://www.ti.com/lit/ug/sprui30b/sprui30b.pdf
> >
> >Keerthy (2):
> >  thermal: omap: dra752: Remove TSHUT configuration
> >  thermal: omap: dra752: Remove all TSHUT related definitions
> >
> > drivers/thermal/ti-soc-thermal/dra752-bandgap.h    | 19 ---------------
> > .../thermal/ti-soc-thermal/dra752-thermal-data.c   | 28 +---------------------
> > 2 files changed, 1 insertion(+), 46 deletions(-)
> >

      reply	other threads:[~2017-01-24 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06  6:01 [PATCH 0/2] thermal: omap: dra752: Remove TSHUT configuration Keerthy
2017-01-06  6:01 ` [PATCH 1/2] thermal: arm: " Keerthy
2017-01-06  6:01 ` [PATCH 2/2] thermal: arm: dra752: Remove all TSHUT related definitions Keerthy
2017-01-23 15:19 ` [PATCH 0/2] thermal: omap: dra752: Remove TSHUT configuration Keerthy
2017-01-24 10:13   ` Eduardo Valentin [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=20170124101300.GA21523@localhost.localdomain \
    --to=edubezval@gmail.com \
    --cc=j-keerthy@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rk@ti.com \
    --cc=rui.zhang@intel.com \
    --cc=t-kristo@ti.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).