All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keerthy <j-keerthy@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: <edubezval@gmail.com>, <rui.zhang@intel.com>,
	<linux-omap@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
	<robh+dt@kernel.org>, <t-kristo@ti.com>
Subject: Re: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree
Date: Tue, 7 Mar 2017 12:43:36 +0530	[thread overview]
Message-ID: <1c47d169-7962-2fe7-0635-570881e85e06@ti.com> (raw)
In-Reply-To: <20170306184215.GO20572@atomide.com>



On Tuesday 07 March 2017 12:12 AM, Tony Lindgren wrote:
> * Keerthy <j-keerthy@ti.com> [170301 02:31]:
>> Currently the slope and offset values for calculating the
>> hot spot temperature of a particular thermal zone is part
>> of driver data. Pass them here instead and obtain the values
>> while of node parsing.
>>
>> Tested for the slope and constant values on DRA7-EVM.
>>
>> Keerthy (7):
>>   ARM: DRA7: Thermal: Add slope and offset values
>>   ARM: OMAP5: Thermal: Add slope and offset values
>>   ARM: OMAP443x: Thermal: Add slope and offset values
>>   ARM: OMAP4460: Thermal: Add slope and offset values
>>   thermal: ti-soc-thermal: Fetch slope and offset from DT
>>   thermal: ti-soc-thermal: Remove redundant constants
>>   thermal: ti-soc-thermal: Remove redundant code
>
> Are the dts changes safe for me to pick separately into
> omap-for-v4.12/dt?

Tony,

Seems like omap3 has no thermal_zone node defined in Device Tree.
It seems like it still uses driver data. I would need to add that as 
well. Can you confirm that? If yes i will send a new series with the 
omap3 device tree changes as well.

Thanks,
Keerthy

>
> Regards,
>
> Tony
>

WARNING: multiple messages have this Message-ID (diff)
From: Keerthy <j-keerthy@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: t-kristo@ti.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, edubezval@gmail.com,
	robh+dt@kernel.org, rui.zhang@intel.com,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree
Date: Tue, 7 Mar 2017 12:43:36 +0530	[thread overview]
Message-ID: <1c47d169-7962-2fe7-0635-570881e85e06@ti.com> (raw)
In-Reply-To: <20170306184215.GO20572@atomide.com>



On Tuesday 07 March 2017 12:12 AM, Tony Lindgren wrote:
> * Keerthy <j-keerthy@ti.com> [170301 02:31]:
>> Currently the slope and offset values for calculating the
>> hot spot temperature of a particular thermal zone is part
>> of driver data. Pass them here instead and obtain the values
>> while of node parsing.
>>
>> Tested for the slope and constant values on DRA7-EVM.
>>
>> Keerthy (7):
>>   ARM: DRA7: Thermal: Add slope and offset values
>>   ARM: OMAP5: Thermal: Add slope and offset values
>>   ARM: OMAP443x: Thermal: Add slope and offset values
>>   ARM: OMAP4460: Thermal: Add slope and offset values
>>   thermal: ti-soc-thermal: Fetch slope and offset from DT
>>   thermal: ti-soc-thermal: Remove redundant constants
>>   thermal: ti-soc-thermal: Remove redundant code
>
> Are the dts changes safe for me to pick separately into
> omap-for-v4.12/dt?

Tony,

Seems like omap3 has no thermal_zone node defined in Device Tree.
It seems like it still uses driver data. I would need to add that as 
well. Can you confirm that? If yes i will send a new series with the 
omap3 device tree changes as well.

Thanks,
Keerthy

>
> Regards,
>
> Tony
>

WARNING: multiple messages have this Message-ID (diff)
From: j-keerthy@ti.com (Keerthy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree
Date: Tue, 7 Mar 2017 12:43:36 +0530	[thread overview]
Message-ID: <1c47d169-7962-2fe7-0635-570881e85e06@ti.com> (raw)
In-Reply-To: <20170306184215.GO20572@atomide.com>



On Tuesday 07 March 2017 12:12 AM, Tony Lindgren wrote:
> * Keerthy <j-keerthy@ti.com> [170301 02:31]:
>> Currently the slope and offset values for calculating the
>> hot spot temperature of a particular thermal zone is part
>> of driver data. Pass them here instead and obtain the values
>> while of node parsing.
>>
>> Tested for the slope and constant values on DRA7-EVM.
>>
>> Keerthy (7):
>>   ARM: DRA7: Thermal: Add slope and offset values
>>   ARM: OMAP5: Thermal: Add slope and offset values
>>   ARM: OMAP443x: Thermal: Add slope and offset values
>>   ARM: OMAP4460: Thermal: Add slope and offset values
>>   thermal: ti-soc-thermal: Fetch slope and offset from DT
>>   thermal: ti-soc-thermal: Remove redundant constants
>>   thermal: ti-soc-thermal: Remove redundant code
>
> Are the dts changes safe for me to pick separately into
> omap-for-v4.12/dt?

Tony,

Seems like omap3 has no thermal_zone node defined in Device Tree.
It seems like it still uses driver data. I would need to add that as 
well. Can you confirm that? If yes i will send a new series with the 
omap3 device tree changes as well.

Thanks,
Keerthy

>
> Regards,
>
> Tony
>

  reply	other threads:[~2017-03-07 20:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 10:29 [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree Keerthy
2017-03-01 10:29 ` Keerthy
2017-03-01 10:29 ` Keerthy
2017-03-01 10:29 ` [PATCH 1/7] ARM: DRA7: Thermal: Add slope and offset values Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29 ` [PATCH 2/7] ARM: OMAP5: " Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29 ` [PATCH 3/7] ARM: OMAP443x: " Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29 ` [PATCH 4/7] ARM: OMAP4460: " Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29 ` [PATCH 5/7] thermal: ti-soc-thermal: Fetch slope and offset from DT Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29 ` [PATCH 6/7] thermal: ti-soc-thermal: Remove redundant constants Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29 ` [PATCH 7/7] thermal: ti-soc-thermal: Remove redundant code Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-01 10:29   ` Keerthy
2017-03-06 18:42 ` [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree Tony Lindgren
2017-03-06 18:42   ` Tony Lindgren
2017-03-06 18:42   ` Tony Lindgren
2017-03-07  7:13   ` Keerthy [this message]
2017-03-07  7:13     ` Keerthy
2017-03-07  7:13     ` Keerthy
2017-03-07 15:12     ` Tony Lindgren
2017-03-07 15:12       ` Tony Lindgren

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=1c47d169-7962-2fe7-0635-570881e85e06@ti.com \
    --to=j-keerthy@ti.com \
    --cc=edubezval@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.