From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933211AbdCGU3L (ORCPT ); Tue, 7 Mar 2017 15:29:11 -0500 Received: from fllnx209.ext.ti.com ([198.47.19.16]:61105 "EHLO fllnx209.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755949AbdCGU3I (ORCPT ); Tue, 7 Mar 2017 15:29:08 -0500 Subject: Re: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree To: Tony Lindgren References: <1488364190-23488-1-git-send-email-j-keerthy@ti.com> <20170306184215.GO20572@atomide.com> CC: , , , , , , , From: Keerthy Message-ID: <1c47d169-7962-2fe7-0635-570881e85e06@ti.com> Date: Tue, 7 Mar 2017 12:43:36 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <20170306184215.GO20572@atomide.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 07 March 2017 12:12 AM, Tony Lindgren wrote: > * Keerthy [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 > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keerthy 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 Message-ID: <1c47d169-7962-2fe7-0635-570881e85e06@ti.com> References: <1488364190-23488-1-git-send-email-j-keerthy@ti.com> <20170306184215.GO20572@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170306184215.GO20572@atomide.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Tony Lindgren 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 List-Id: linux-pm@vger.kernel.org On Tuesday 07 March 2017 12:12 AM, Tony Lindgren wrote: > * Keerthy [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 > From mboxrd@z Thu Jan 1 00:00:00 1970 From: j-keerthy@ti.com (Keerthy) Date: Tue, 7 Mar 2017 12:43:36 +0530 Subject: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree In-Reply-To: <20170306184215.GO20572@atomide.com> References: <1488364190-23488-1-git-send-email-j-keerthy@ti.com> <20170306184215.GO20572@atomide.com> Message-ID: <1c47d169-7962-2fe7-0635-570881e85e06@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tuesday 07 March 2017 12:12 AM, Tony Lindgren wrote: > * Keerthy [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 >