Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1590247 > unrolled thread
| Started by | Keerthy <j-keerthy@ti.com> |
|---|---|
| First post | 2017-03-01 12:10 +0100 |
| Last post | 2017-03-07 21:30 +0100 |
| Articles | 6 — 2 participants |
Back to article view | Back to linux.kernel
[PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree Keerthy <j-keerthy@ti.com> - 2017-03-01 12:10 +0100
[PATCH 1/7] ARM: DRA7: Thermal: Add slope and offset values Keerthy <j-keerthy@ti.com> - 2017-03-01 12:10 +0100
[PATCH 4/7] ARM: OMAP4460: Thermal: Add slope and offset values Keerthy <j-keerthy@ti.com> - 2017-03-01 15:10 +0100
Re: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree Tony Lindgren <tony@atomide.com> - 2017-03-06 19:50 +0100
Re: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree Tony Lindgren <tony@atomide.com> - 2017-03-07 16:20 +0100
Re: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree Keerthy <j-keerthy@ti.com> - 2017-03-07 21:30 +0100
| From | Keerthy <j-keerthy@ti.com> |
|---|---|
| Date | 2017-03-01 12:10 +0100 |
| Subject | [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree |
| Message-ID | <tg9PQ-1LH-23@gated-at.bofh.it> |
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 arch/arm/boot/dts/dra7.dtsi | 17 +++ arch/arm/boot/dts/omap443x.dtsi | 4 + arch/arm/boot/dts/omap4460.dtsi | 4 + arch/arm/boot/dts/omap5.dtsi | 9 ++ .../thermal/ti-soc-thermal/dra752-thermal-data.c | 10 -- .../thermal/ti-soc-thermal/omap4-thermal-data.c | 4 - .../thermal/ti-soc-thermal/omap5-thermal-data.c | 4 - drivers/thermal/ti-soc-thermal/ti-thermal-common.c | 164 ++------------------- 8 files changed, 45 insertions(+), 171 deletions(-) -- 1.9.1
[toc] | [next] | [standalone]
| From | Keerthy <j-keerthy@ti.com> |
|---|---|
| Date | 2017-03-01 12:10 +0100 |
| Subject | [PATCH 1/7] ARM: DRA7: Thermal: Add slope and offset values |
| Message-ID | <tgaiR-2ds-13@gated-at.bofh.it> |
| In reply to | #1590247 |
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.
Signed-off-by: Keerthy <j-keerthy@ti.com>
---
arch/arm/boot/dts/dra7.dtsi | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index 2c9e56f..10e09dc 100644
--- a/arch/arm/boot/dts/dra7.dtsi
+++ b/arch/arm/boot/dts/dra7.dtsi
@@ -1982,6 +1982,23 @@
&cpu_thermal {
polling-delay = <500>; /* milliseconds */
+ coefficients = <0 2000>;
+};
+
+&gpu_thermal {
+ coefficients = <0 2000>;
+};
+
+&core_thermal {
+ coefficients = <0 2000>;
+};
+
+&dspeve_thermal {
+ coefficients = <0 2000>;
+};
+
+&iva_thermal {
+ coefficients = <0 2000>;
};
/include/ "dra7xx-clocks.dtsi"
--
1.9.1
[toc] | [prev] | [next] | [standalone]
| From | Keerthy <j-keerthy@ti.com> |
|---|---|
| Date | 2017-03-01 15:10 +0100 |
| Subject | [PATCH 4/7] ARM: OMAP4460: Thermal: Add slope and offset values |
| Message-ID | <tgd73-47I-15@gated-at.bofh.it> |
| In reply to | #1590247 |
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.
Signed-off-by: Keerthy <j-keerthy@ti.com>
---
arch/arm/boot/dts/omap4460.dtsi | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/omap4460.dtsi b/arch/arm/boot/dts/omap4460.dtsi
index ef66e12..c43f2a2 100644
--- a/arch/arm/boot/dts/omap4460.dtsi
+++ b/arch/arm/boot/dts/omap4460.dtsi
@@ -90,4 +90,8 @@
};
+&cpu_thermal {
+ coefficients = <348 (-9301)>;
+};
+
/include/ "omap446x-clocks.dtsi"
--
1.9.1
[toc] | [prev] | [next] | [standalone]
| From | Tony Lindgren <tony@atomide.com> |
|---|---|
| Date | 2017-03-06 19:50 +0100 |
| Subject | Re: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree |
| Message-ID | <ti5RM-3Nc-27@gated-at.bofh.it> |
| In reply to | #1590247 |
* 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? Regards, Tony
[toc] | [prev] | [next] | [standalone]
| From | Tony Lindgren <tony@atomide.com> |
|---|---|
| Date | 2017-03-07 16:20 +0100 |
| Subject | Re: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree |
| Message-ID | <tip47-X4-39@gated-at.bofh.it> |
| In reply to | #1593591 |
* 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
[toc] | [prev] | [next] | [standalone]
| From | Keerthy <j-keerthy@ti.com> |
|---|---|
| Date | 2017-03-07 21:30 +0100 |
| Subject | Re: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree |
| Message-ID | <tip47-X4-41@gated-at.bofh.it> |
| In reply to | #1593591 |
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 >
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web