Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1364562 > unrolled thread

Re: [PATCH V8 00/14] Add T210 support in Tegra soctherm

Started byWei Ni <wni@nvidia.com>
First post2016-03-25 06:40 +0100
Last post2016-03-29 12:20 +0200
Articles 7 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH V8 00/14] Add T210 support in Tegra soctherm Wei Ni <wni@nvidia.com> - 2016-03-25 06:40 +0100
    Re: [PATCH V8 00/14] Add T210 support in Tegra soctherm Eduardo Valentin <edubezval@gmail.com> - 2016-03-28 15:40 +0200
    Re: [PATCH V8 00/14] Add T210 support in Tegra soctherm Eduardo Valentin <edubezval@gmail.com> - 2016-03-29 05:10 +0200
      Re: [PATCH V8 00/14] Add T210 support in Tegra soctherm Eduardo Valentin <edubezval@gmail.com> - 2016-03-29 05:40 +0200
        Re: [PATCH V8 00/14] Add T210 support in Tegra soctherm Wei Ni <wni@nvidia.com> - 2016-03-29 06:30 +0200
      Re: [PATCH V8 00/14] Add T210 support in Tegra soctherm Wei Ni <wni@nvidia.com> - 2016-03-29 07:00 +0200
        Re: [PATCH V8 00/14] Add T210 support in Tegra soctherm Wei Ni <wni@nvidia.com> - 2016-03-29 12:20 +0200

#1364562 — Re: [PATCH V8 00/14] Add T210 support in Tegra soctherm

FromWei Ni <wni@nvidia.com>
Date2016-03-25 06:40 +0100
SubjectRe: [PATCH V8 00/14] Add T210 support in Tegra soctherm
Message-ID<rgsDw-5us-3@gated-at.bofh.it>
Hi, Eduardo
Will you take this series, it seems no more comments.

Thanks.
Wei.

On 2016年03月16日 16:55, 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 v7 series is in:
> https://patchwork.kernel.org/patch/8561681/
> The v6 series is in:
> https://lkml.org/lkml/2016/2/22/66
> The v5 series is in:
> http://www.spinics.net/lists/linux-tegra/msg25079.html
> The v4 series is in:
> http://www.spinics.net/lists/linux-tegra/msg24972.html
> The V3 series is in:
> http://www.spinics.net/lists/linux-tegra/msg24911.html
> The V2 series is in:
> http://www.spinics.net/lists/linux-tegra/msg24901.html
> The V1 series is in:
> http://www.spinics.net/lists/linux-tegra/msg24808.html
> 
> Main changes from V7:
> 1. Split PM support patch into three smaller patches.
> 2. Few changes per Eduardo's comments.
> 
> Main changes from V6:
> 1. rebased patches on Eduardo's
> [PATCH 00/13] thermal: convert users of thermal_zone_of_sensor_register to devm_
> 
> Main changes from V5:
> 1. Change to use linux thermal framework to implement
> thermtrip funciton, per Rob's comment.
> 2. Add .set_trip_temp() in of-thermal driver, so that
> we can set trips on hardware.
> 
> Main changes from V4:
> 1. Change description of devicetree binding per Rob's comment.
> 2. Call of_node_put to decrement refcount of the node.
> 
> Main changes from V3:
> 1. Change structures to "const" in chip specific files.
> 2. Minor changes per Thieery's comments.
> 
> 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 (14):
>   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 Tegra210 specific SOC_THERM driver
>   thermal: tegra: add a debugfs to show registers
>   thermal: of-thermal: allow setting trip_temp on hardware
>   of: add notes of critical trips for soctherm
>   thermal: tegra: add thermtrip function
>   thermal: tegra: handle clocks in one function
>   thermal: tegra: handle HW initialization in one funcotion
>   thermal: tegra: add PM support
>   arm64: tegra: add soctherm node for Tegra210
>   arm: tegra: set critical trips for Tegra124
> 
>  .../devicetree/bindings/thermal/tegra-soctherm.txt |  12 +
>  arch/arm/boot/dts/tegra124-jetson-tk1.dts          |  18 +-
>  arch/arm/boot/dts/tegra124.dtsi                    |  48 ++
>  arch/arm64/boot/dts/nvidia/tegra210.dtsi           |  92 +++
>  drivers/thermal/Kconfig                            |  12 +-
>  drivers/thermal/Makefile                           |   2 +-
>  drivers/thermal/of-thermal.c                       |   8 +
>  drivers/thermal/tegra/Kconfig                      |  13 +
>  drivers/thermal/tegra/Makefile                     |   5 +
>  drivers/thermal/tegra/soctherm-fuse.c              | 169 +++++
>  drivers/thermal/tegra/soctherm.c                   | 682 +++++++++++++++++++++
>  drivers/thermal/tegra/soctherm.h                   | 123 ++++
>  drivers/thermal/tegra/tegra124-soctherm.c          | 196 ++++++
>  drivers/thermal/tegra/tegra210-soctherm.c          | 197 ++++++
>  drivers/thermal/tegra_soctherm.c                   | 463 --------------
>  include/dt-bindings/thermal/tegra124-soctherm.h    |   1 +
>  include/linux/thermal.h                            |   1 +
>  17 files changed, 1553 insertions(+), 489 deletions(-)
>  create mode 100644 drivers/thermal/tegra/Kconfig
>  create mode 100644 drivers/thermal/tegra/Makefile
>  create mode 100644 drivers/thermal/tegra/soctherm-fuse.c
>  create mode 100644 drivers/thermal/tegra/soctherm.c
>  create mode 100644 drivers/thermal/tegra/soctherm.h
>  create mode 100644 drivers/thermal/tegra/tegra124-soctherm.c
>  create mode 100644 drivers/thermal/tegra/tegra210-soctherm.c
>  delete mode 100644 drivers/thermal/tegra_soctherm.c
>

[toc] | [next] | [standalone]

#1365497

FromEduardo Valentin <edubezval@gmail.com>
Date2016-03-28 15:40 +0200
Message-ID<rhFyF-7M5-15@gated-at.bofh.it>
In reply to#1364562
On Fri, Mar 25, 2016 at 01:37:17PM +0800, Wei Ni wrote:
> Hi, Eduardo
> Will you take this series, it seems no more comments.

Yes, now that the merge window is closed, I will have another look on
it. It is  on my todo queue.

[toc] | [prev] | [next] | [standalone]

#1365816

FromEduardo Valentin <edubezval@gmail.com>
Date2016-03-29 05:10 +0200
Message-ID<rhScx-8rb-3@gated-at.bofh.it>
In reply to#1364562
On Fri, Mar 25, 2016 at 01:37:17PM +0800, Wei Ni wrote:
> Hi, Eduardo
> Will you take this series, it seems no more comments.

Yeah, I am taking a look at it. Something is fishy about it. Patch 04
does not apply cleanly. Also, why did you split the patches into two
email threads, one which is 1-4 and another one is 5-14?

I have ammended patch 04 at my side, but you need to validate your
series is one piece (please check my tree and linux-next).

BR,

Eduardo Valentin

>

[toc] | [prev] | [next] | [standalone]

#1365830

FromEduardo Valentin <edubezval@gmail.com>
Date2016-03-29 05:40 +0200
Message-ID<rhSFA-8V-25@gated-at.bofh.it>
In reply to#1365816
On Mon, Mar 28, 2016 at 08:04:41PM -0700, Eduardo Valentin wrote:
> On Fri, Mar 25, 2016 at 01:37:17PM +0800, Wei Ni wrote:
> > Hi, Eduardo
> > Will you take this series, it seems no more comments.
> 
> Yeah, I am taking a look at it. Something is fishy about it. Patch 04
> does not apply cleanly. Also, why did you split the patches into two
> email threads, one which is 1-4 and another one is 5-14?
> 
> I have ammended patch 04 at my side, but you need to validate your
> series is one piece (please check my tree and linux-next).

This didn't quite work. Please refresh your series on top of my fixes
branch so I can apply your series cleanly.

> 
> BR,
> 
> Eduardo Valentin
> 
> >

[toc] | [prev] | [next] | [standalone]

#1365840

FromWei Ni <wni@nvidia.com>
Date2016-03-29 06:30 +0200
Message-ID<rhTrX-RX-9@gated-at.bofh.it>
In reply to#1365830

On 2016年03月29日 11:29, Eduardo Valentin wrote:
> On Mon, Mar 28, 2016 at 08:04:41PM -0700, Eduardo Valentin wrote:
>> On Fri, Mar 25, 2016 at 01:37:17PM +0800, Wei Ni wrote:
>>> Hi, Eduardo
>>> Will you take this series, it seems no more comments.
>>
>> Yeah, I am taking a look at it. Something is fishy about it. Patch 04
>> does not apply cleanly. Also, why did you split the patches into two
>> email threads, one which is 1-4 and another one is 5-14?
>>
>> I have ammended patch 04 at my side, but you need to validate your
>> series is one piece (please check my tree and linux-next).
> 
> This didn't quite work. Please refresh your series on top of my fixes
> branch so I can apply your series cleanly.

Yes, I will do it.

> 
>>
>> BR,
>>
>> Eduardo Valentin
>>
>>>

[toc] | [prev] | [next] | [standalone]

#1365853

FromWei Ni <wni@nvidia.com>
Date2016-03-29 07:00 +0200
Message-ID<rhTUZ-12t-1@gated-at.bofh.it>
In reply to#1365816

On 2016年03月29日 11:04, Eduardo Valentin wrote:
> On Fri, Mar 25, 2016 at 01:37:17PM +0800, Wei Ni wrote:
>> Hi, Eduardo
>> Will you take this series, it seems no more comments.
> 
> Yeah, I am taking a look at it. Something is fishy about it. Patch 04
> does not apply cleanly. Also, why did you split the patches into two
> email threads, one which is 1-4 and another one is 5-14?

Sorry, what do you mean "split the patches into two email threads"? And what's
the 1-4 and 5-14?
I think I didn't split my patches into two email thread.

Thanks.
Wei.

> 
> I have ammended patch 04 at my side, but you need to validate your
> series is one piece (please check my tree and linux-next).
> 
> BR,
> 
> Eduardo Valentin
> 
>>

[toc] | [prev] | [next] | [standalone]

#1366110

FromWei Ni <wni@nvidia.com>
Date2016-03-29 12:20 +0200
Message-ID<rhYUG-4CQ-19@gated-at.bofh.it>
In reply to#1365853

On 2016年03月29日 12:57, Wei Ni wrote:
> 
> 
> On 2016年03月29日 11:04, Eduardo Valentin wrote:
>> On Fri, Mar 25, 2016 at 01:37:17PM +0800, Wei Ni wrote:
>>> Hi, Eduardo
>>> Will you take this series, it seems no more comments.
>>
>> Yeah, I am taking a look at it. Something is fishy about it. Patch 04
>> does not apply cleanly. Also, why did you split the patches into two
>> email threads, one which is 1-4 and another one is 5-14?
> 
> Sorry, what do you mean "split the patches into two email threads"? And what's
> the 1-4 and 5-14?
> I think I didn't split my patches into two email thread.

I think I knew what's your mean.
When I use "git send-email --to=xxx *.patch" to send patches, I hit " 4.4.2
Message submission rate for this client has exceeded the configured limit".
So I split them to send.
And I didn't realized it will cause problems before I sending out V9 series, so
I sent V9 patches one by one, they appear as individual emails on the mailing
list, not as a thread.
I will check my email system and resend them.

Thanks.
Wei.

> 
> Thanks.
> Wei.
> 
>>
>> I have ammended patch 04 at my side, but you need to validate your
>> series is one piece (please check my tree and linux-next).
>>
>> BR,
>>
>> Eduardo Valentin
>>
>>>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web