lkml.org 
[lkml]   [2017]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree
* Keerthy <j-keerthy@ti.com> [170306 23:15]:
>
>
> 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.

OK cool. It might be worth checking how it was configured with
the legacy platform data.

Regards,

Tony

\
 
 \ /
  Last update: 2017-03-07 16:14    [W:1.215 / U:0.320 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site