devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Wei Ni <wni@nvidia.com>,
	edubezval@gmail.com, thierry.reding@gmail.com,
	robh+dt@kernel.org
Cc: MLongnecker@nvidia.com, swarren@wwwdotorg.org,
	mikko.perttunen@kapsi.fi, linux-tegra@vger.kernel.org,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 00/11] Add HW throttle for Tegra soctherm
Date: Fri, 19 Aug 2016 15:15:24 +0800	[thread overview]
Message-ID: <1471590924.2691.34.camel@intel.com> (raw)
In-Reply-To: <5746C4FD.9070909@nvidia.com>

On 四, 2016-05-26 at 17:42 +0800, Wei Ni wrote:
> Hi,
> Does there have any comments on this series?
> Let me know if someone has suggestions.
> 
I have no objections to this patch set.
As 10 patches out of 11, in this patch series, contain changes out of
thermal scope, if you prefer this patch set go through thermal tree, I
still need ACKs for the changes out of thermal scope.

thanks,
rui

> Thanks.
> Wei.
> 
> On 05/11/2016 06:20 PM, Wei Ni wrote:
> > 
> > This series add following functions for Tegra soctherm:
> > 1. add HW throttle function.
> > 2. enable soctherm node for Tegra124, Tegra132, Tegra210, and
> > set "critical", "hot" trips for them.
> > 
> > Main changes from v4:
> > 1. drop the "nvidia" prefix from the node name, per Rob's comments.
> > 
> > Main changes from v3:
> > 1. change some properties'name and descriptions, per Rob's
> > comments.
> > 2. change the corresponding driver codes.
> > 
> > Main changes from v2:
> > 1. improve the of-binding, per Eduardo's comments, and
> > change the corresponding driver codes.
> > 2. move two setting critical trip patches in this series,
> > 3. fix some bugs in dts changes.
> > 
> > Main changes from v1:
> > 1. use readl/writel instead of __raw_readl/__raw_writel.
> > 2. rebase on the linux-next.
> > 
> > The v1 series is in:
> > https://lkml.org/lkml/2016/3/31/230
> > 
> > The v2 series is in:
> > https://lkml.org/lkml/2016/4/26/1577
> > 
> > The v3 series is in:
> > https://lkml.org/lkml/2016/5/3/274
> > 
> > The v4 series is in:
> > https://lkml.org/lkml/2016/5/9/45
> > 
> > Wei Ni (11):
> >   of: Add bindings of hw throttle for Tegra soctherm
> >   thermal: tegra: add hw-throttle function
> >   thermal: tegra: add hw-throttle for Tegra132
> >   arm: tegra: set critical trips for Tegra124
> >   arm: tegra: set hot trips for Tegra124
> >   arm64: tegra: use tegra132-soctherm for Tegra132
> >   arm64: tegra: set critical trips for Tegra132
> >   arm64: tegra: set hot trips for Tegra132
> >   arm64: tegra: add soctherm node for Tegra210
> >   arm64: tegra: set critical trips for Tegra210
> >   arm64: tegra: set hot trips for Tegra210
> > 
> >  .../bindings/thermal/nvidia,tegra124-soctherm.txt  | 121 ++-
> >  arch/arm/boot/dts/tegra124-jetson-tk1.dts          |  18 +-
> >  arch/arm/boot/dts/tegra124.dtsi                    |  83 +-
> >  arch/arm64/boot/dts/nvidia/tegra132.dtsi           | 119 ++-
> >  arch/arm64/boot/dts/nvidia/tegra210.dtsi           | 127 ++++
> >  drivers/thermal/tegra/soctherm.c                   | 842
> > ++++++++++++++++++++-
> >  drivers/thermal/tegra/soctherm.h                   |  10 +
> >  drivers/thermal/tegra/tegra124-soctherm.c          |  18 +
> >  drivers/thermal/tegra/tegra132-soctherm.c          |  18 +
> >  drivers/thermal/tegra/tegra210-soctherm.c          |  18 +
> >  include/dt-bindings/thermal/tegra124-soctherm.h    |   5 +
> >  11 files changed, 1344 insertions(+), 35 deletions(-)
> > 

  reply	other threads:[~2016-08-19  7:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 10:20 [PATCH v5 00/11] Add HW throttle for Tegra soctherm Wei Ni
2016-05-11 10:20 ` [PATCH v5 03/11] thermal: tegra: add hw-throttle for Tegra132 Wei Ni
2016-05-11 10:20 ` [PATCH v5 04/11] arm: tegra: set critical trips for Tegra124 Wei Ni
2016-05-11 10:20 ` [PATCH v5 05/11] arm: tegra: set hot " Wei Ni
     [not found] ` <1462962026-19653-1-git-send-email-wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-11 10:20   ` [PATCH v5 01/11] of: Add bindings of hw throttle for Tegra soctherm Wei Ni
2016-05-16 15:01     ` Rob Herring
2016-05-11 10:20   ` [PATCH v5 02/11] thermal: tegra: add hw-throttle function Wei Ni
2016-05-11 10:20   ` [PATCH v5 06/11] arm64: tegra: use tegra132-soctherm for Tegra132 Wei Ni
2016-05-26  9:42   ` [PATCH v5 00/11] Add HW throttle for Tegra soctherm Wei Ni
2016-08-19  7:15     ` Zhang Rui [this message]
     [not found]       ` <1471590924.2691.34.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-08-31  3:07         ` Wei Ni
2016-05-11 10:20 ` [PATCH v5 07/11] arm64: tegra: set critical trips for Tegra132 Wei Ni
2016-05-11 10:20 ` [PATCH v5 08/11] arm64: tegra: set hot " Wei Ni
2016-05-11 10:20 ` [PATCH v5 09/11] arm64: tegra: add soctherm node for Tegra210 Wei Ni
2016-05-11 10:20 ` [PATCH v5 10/11] arm64: tegra: set critical trips " Wei Ni
2016-05-11 10:20 ` [PATCH v5 11/11] arm64: tegra: set hot " Wei Ni

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=1471590924.2691.34.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=MLongnecker@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mikko.perttunen@kapsi.fi \
    --cc=robh+dt@kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.com \
    --cc=wni@nvidia.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).