[lkml]   [2013]   [Aug]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[RFC PATCH 00/14] RFCv2: device thermal limits represented in device tree nodes
Hello all,

First of all, apologize for the very late answer. But I am resuming this work.

This RFC is about describing hardware thermal limits using device tree.

Based on the discussion on the first RFC:

I have changed the code and the device tree bindings as follows:
1. Now bindings may have several thermal zones per device (req. by Wei Ni)
2. The constants used are now using C preprocessor macros (as per Stephen suggestion)
3. Improved the bindings to have a better representation of links between
involved entities (thermal zone, cooling devices, sensors), as suggested
by Pawel and Mark.
4. Couple of changes in code, as per previous reviews.
5. Removed policies from DT bindings.

In summary, based on the discussion of the first RFC, now the idea is
to have thermal zones nodes describing the thermal zones
and the hardware limits. Then sensor devices nodes will point to
thermal zones via phandles and cooling device will also point to
thermal zone via phandles.

So, I am also posting the patch series to dt mailing list as requested.

Please refer to patch 02/14 to a documentation of what I am proposing.

This patch series includes:
a. Required changes in cpufreq-cpu0 driver so that it loads cooling device
when requested.
b. The thermal zone builder based on thermal bindings
c. Changes in sensor drivers (as examples)
d. Changes in device tree DTS files (as examples)

This patch series depends on the fixes I sent to linux-pm:

In the above link you will find also the request to have a flag to
determine if virtual hwmon device will be created, based on thermal device.

All best,

Eduardo Valentin (14):
cpufreq: cpufreq-cpu0: add dt node parsing for 'cooling-zones'
drivers: thermal: introduce device tree parser
hwmon: lm75: expose to thermal fw via DT nodes
hwmon: tmp102: expose to thermal fw via DT nodes
thermal: ti-soc-thermal: use thermal DT infrastructure
arm: dts: add omap4 CPU thermal data
arm: dts: add omap4430 thermal data
arm: dts: add omap4460 thermal data
arm: dts: point to cooling-zones on omap4430 cpu node
arm: dts: point to cooling-zones on omap4460 cpu node
arm: dts: add omap5 GPU thermal data
arm: dts: add omap5 CORE thermal data
arm: dts: add omap5 thermal data
arm: dts: point to cooling-zones on omap5 cpu node

.../devicetree/bindings/cpufreq/cpufreq-cpu0.txt | 4 +
.../devicetree/bindings/thermal/thermal.txt | 160 +++++++
arch/arm/boot/dts/omap4-cpu-thermal.dtsi | 40 ++
arch/arm/boot/dts/omap443x.dtsi | 6 +
arch/arm/boot/dts/omap4460.dtsi | 6 +
arch/arm/boot/dts/omap5-core-thermal.dtsi | 27 ++
arch/arm/boot/dts/omap5-gpu-thermal.dtsi | 27 ++
arch/arm/boot/dts/omap5.dtsi | 10 +
drivers/cpufreq/cpufreq-cpu0.c | 12 +
drivers/hwmon/lm75.c | 31 ++
drivers/hwmon/tmp102.c | 26 ++
drivers/thermal/Kconfig | 13 +
drivers/thermal/Makefile | 1 +
drivers/thermal/thermal_dt.c | 473 +++++++++++++++++++++
drivers/thermal/ti-soc-thermal/ti-thermal-common.c | 52 ++-
include/dt-bindings/thermal/thermal.h | 27 ++
include/linux/thermal.h | 3 +
17 files changed, 907 insertions(+), 11 deletions(-)
create mode 100644 Documentation/devicetree/bindings/thermal/thermal.txt
create mode 100644 arch/arm/boot/dts/omap4-cpu-thermal.dtsi
create mode 100644 arch/arm/boot/dts/omap5-core-thermal.dtsi
create mode 100644 arch/arm/boot/dts/omap5-gpu-thermal.dtsi
create mode 100644 drivers/thermal/thermal_dt.c
create mode 100644 include/dt-bindings/thermal/thermal.h


 \ /
  Last update: 2013-08-24 01:41    [W:0.103 / U:1.496 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site