linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Wei Ni <wni@nvidia.com>
Cc: rui.zhang@intel.com, MLongnecker@nvidia.com,
	swarren@wwwdotorg.org, mikko.perttunen@kapsi.fi,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 00/11] Add T210 support in Tegra soctherm
Date: Thu, 21 Jan 2016 15:56:57 +0100	[thread overview]
Message-ID: <20160121145657.GF32301@ulmo> (raw)
In-Reply-To: <1453111356-12298-1-git-send-email-wni@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]

On Mon, Jan 18, 2016 at 06:02:25PM +0800, Wei Ni wrote:
> This patchset adds following functions for tegra_soctherm driver:
> 1. add T210 support.
> 2. export debugfs to show some registers.
> 3. add thermtrip funciton.
> 4. add suspend/resume function.
> 
> The V1 serial is in:
> http://www.spinics.net/lists/linux-tegra/msg24808.html
> The V2 serial is in:
> http://www.spinics.net/lists/linux-tegra/msg24901.html
> 
> Main changes from V2:
> 1. Fix build error in patch [1/11].
> 2. Use of_get_child_by_name instead of of_find_node_by_name in patch [8/11].
> 3. Use debugfs_remove_recursive to remove debugfs in patch [6/11].
> 
> Main changes from V1:
> 1. Use the new type to handl different Tegra chips in one driver,
> which suggested by Thierry.
> 2. Changes per Thieery's other comments.
> 
> Wei Ni (11):
>   thermal: tegra: move tegra thermal files into tegra directory
>   thermal: tegra: combine sensor group-related data
>   thermal: tegra: get rid of PDIV/HOTSPOT hack
>   thermal: tegra: split tegra_soctherm driver
>   thermal: tegra: add T210-specific SOC_THERM driver
>   thermal: tegra: add a debugfs to show registers
>   of: Add bindings of hw-trips for soctherm
>   thermal: tegra: add thermtrip function
>   thermal: tegra: add PM support
>   arm64: tegra: add soctherm node for Tegra210
>   ARM: tegra: set hw trips for Tegra124

Hi Wei,

This series looks mostly good to me. I've commented on a couple of minor
things as replies to the individual patches.

On a higher level, what's the test procedure that we can use to validate
that this code works?

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-01-21 14:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 10:02 [PATCH V3 00/11] Add T210 support in Tegra soctherm Wei Ni
2016-01-18 10:02 ` [PATCH V3 01/11] thermal: tegra: move tegra thermal files into tegra directory Wei Ni
2016-01-18 10:02 ` [PATCH V3 02/11] thermal: tegra: combine sensor group-related data Wei Ni
2016-01-18 10:02 ` [PATCH V3 03/11] thermal: tegra: get rid of PDIV/HOTSPOT hack Wei Ni
2016-01-18 10:02 ` [PATCH V3 04/11] thermal: tegra: split tegra_soctherm driver Wei Ni
2016-01-21 14:46   ` Thierry Reding
2016-01-22  8:52     ` Wei Ni
2016-01-21 14:56 ` Thierry Reding [this message]
2016-01-22  7:27   ` [PATCH V3 00/11] Add T210 support in Tegra soctherm 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=20160121145657.GF32301@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=MLongnecker@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mikko.perttunen@kapsi.fi \
    --cc=rui.zhang@intel.com \
    --cc=swarren@wwwdotorg.org \
    --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).