linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
	linux-pm@vger.kernel.org,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	linux-renesas-soc@vger.kernel.org,
	"Zhang Rui" <rui.zhang@intel.com>
Subject: Re: [PATCH v3 0/7] thermal: rcar_gen3_thermal: add support for interrupt triggerd trip points
Date: Thu, 30 Mar 2017 21:56:49 -0700	[thread overview]
Message-ID: <20170331045647.GA2194@localhost.localdomain> (raw)
In-Reply-To: <20170329205139.GB1440@katana>

On Wed, Mar 29, 2017 at 10:51:39PM +0200, Wolfram Sang wrote:
> On Wed, Mar 29, 2017 at 08:43:49PM +0200, Niklas Söderlund wrote:
> > Hi,
> > 
> > This series adds support for hardware backed trip point windows. It is
> > based on top of v4.11-rc1 and is tested on R-Car H3 and M3-W.
> > 
> > The series starts out by fixing three issues (1/7, 2/7, 3/7) that should
> > have been fixed by me before the initial driver where submitted to
> > upstream. Sorry for not spotting the issues sooner.
> > 
> > The series then extends the rcar_gen3_thermal driver with hardware
> > interrupts for trip point windows by implementing the .set_trips()
> > callback of struct thermal_zone_of_device_ops (4/7, 5/7). It then adds
> > suspend and resume handlers so that the hardware interrupts are
> > preserved across suspend/resume cycles (6/7, 7/7).
> 
> Thanks, Niklas! From my PoV, this series is good to go upstream!
> 
Agreed here. Good job with the patches Niklas. Given the nature of
changes in the driver, I am allowing some time for them to sit on
linux-next. Queued them on my branch -linus, for next merge window.

      reply	other threads:[~2017-03-31  4:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 18:43 [PATCH v3 0/7] thermal: rcar_gen3_thermal: add support for interrupt triggerd trip points Niklas Söderlund
2017-03-29 18:43 ` [PATCH v3 1/7] thermal: rcar_gen3_thermal: add delay in .thermal_init on r8a7796 Niklas Söderlund
2017-03-29 18:43 ` [PATCH v3 2/7] thermal: rcar_gen3_thermal: remove unneeded mutex Niklas Söderlund
2017-03-29 18:43 ` [PATCH v3 3/7] thermal: rcar_gen3_thermal: check that TSC exists before memory allocation Niklas Söderlund
2017-03-29 18:43 ` [PATCH v3 4/7] thermal: rcar_gen3_thermal: record and check number of TSCs found Niklas Söderlund
2017-03-29 18:43 ` [PATCH v3 5/7] thermal: rcar_gen3_thermal: enable hardware interrupts for trip points Niklas Söderlund
2017-03-29 20:50   ` Wolfram Sang
2017-03-29 18:43 ` [PATCH v3 6/7] thermal: rcar_gen3_thermal: store device match data in private structure Niklas Söderlund
2017-03-29 18:43 ` [PATCH v3 7/7] thermal: rcar_gen3_thermal: add suspend and resume support Niklas Söderlund
2017-03-29 20:51 ` [PATCH v3 0/7] thermal: rcar_gen3_thermal: add support for interrupt triggerd trip points Wolfram Sang
2017-03-31  4:56   ` 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=20170331045647.GA2194@localhost.localdomain \
    --to=edubezval@gmail.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=rui.zhang@intel.com \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=wsa@the-dreams.de \
    /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).