[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170306184215.GO20572@atomide.com>
Date: Mon, 6 Mar 2017 10:42:16 -0800
From: Tony Lindgren <tony@...mide.com>
To: Keerthy <j-keerthy@...com>
Cc: edubezval@...il.com, rui.zhang@...el.com,
linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
robh+dt@...nel.org, t-kristo@...com
Subject: Re: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data
to device tree
* Keerthy <j-keerthy@...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?
Regards,
Tony
Powered by blists - more mailing lists