Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1336086 > unrolled thread
| Started by | Krzysztof Kozlowski <k.kozlowski@samsung.com> |
|---|---|
| First post | 2016-02-17 08:00 +0100 |
| Last post | 2016-02-18 04:20 +0100 |
| Articles | 9 — 4 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
[RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load Krzysztof Kozlowski <k.kozlowski@samsung.com> - 2016-02-17 08:00 +0100
Re: [RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load Anand Moon <linux.amoon@gmail.com> - 2016-02-17 21:00 +0100
Re: [RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load Krzysztof Kozlowski <k.kozlowski@samsung.com> - 2016-02-18 02:50 +0100
Re: [RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load Viresh Kumar <viresh.kumar@linaro.org> - 2016-02-18 03:40 +0100
Re: [RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load Anand Moon <linux.amoon@gmail.com> - 2016-02-18 04:00 +0100
Re: [RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load Krzysztof Kozlowski <k.kozlowski@samsung.com> - 2016-02-18 05:50 +0100
Re: [RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load Marek Szyprowski <m.szyprowski@samsung.com> - 2016-02-18 11:00 +0100
Re: [RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load Krzysztof Kozlowski <k.kozlowski@samsung.com> - 2016-02-19 01:00 +0100
Re: [RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load Anand Moon <linux.amoon@gmail.com> - 2016-02-18 04:20 +0100
| From | Krzysztof Kozlowski <k.kozlowski@samsung.com> |
|---|---|
| Date | 2016-02-17 08:00 +0100 |
| Subject | [RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load |
| Message-ID | <r34fE-2FN-11@gated-at.bofh.it> |
After adding cpufreq-dt support to Exynos542x, the Odroid XU3-Lite can
be easily overheated when launching eight CPU-intensive tasks:
thermal thermal_zone3: critical temperature reached(121 C),shutting down
This seems to be specific to Odroid XU3-Lite board which officially
supports lower frequencies than regular XU3 or XU4. When working at
maximum CPU speed (1800 MHz big and 1300 MHz LITTLE) in warmer place for
longer time, the fan fails to cool down the board and it reaches
critical temperature.
Add CPU cooling to Exynos5422/5800 to fix this issue. When reaching 95
degrees of Celsius, the board will slow down by 3 steps (around
1400/1000 MHz). When reaching 110 degrees of Celsius go to 600 MHz.
Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
---
arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi | 41 +++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
index 2b289d7c0d13..66073ce29aee 100644
--- a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
+++ b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
@@ -34,6 +34,16 @@
hysteresis = <5000>; /* millicelsius */
type = "active";
};
+ cpu_alert3: cpu-alert-3 {
+ temperature = <95000>; /* millicelsius */
+ hysteresis = <5000>; /* millicelsius */
+ type = "passive";
+ };
+ cpu_alert4: cpu-alert-4 {
+ temperature = <110000>; /* millicelsius */
+ hysteresis = <5000>; /* millicelsius */
+ type = "passive";
+ };
cpu_crit0: cpu-crit-0 {
temperature = <120000>; /* millicelsius */
hysteresis = <0>; /* millicelsius */
@@ -53,6 +63,37 @@
trip = <&cpu_alert2>;
cooling-device = <&fan0 2 3>;
};
+
+ /*
+ * When reaching cpu_alert3, reduce CPU
+ * by 3 steps. On Exynos5422/5800 that would
+ * be: 1400 MHz and 1000 MHz.
+ */
+ map3 {
+ trip = <&cpu_alert3>;
+ cooling-device = <&cpu0 3 3>;
+ };
+ map4 {
+ trip = <&cpu_alert3>;
+ cooling-device = <&cpu4 3 3>;
+ };
+
+ /*
+ * When reaching cpu_alert4, reduce CPU
+ * to 600 MHz (11 steps for big, 7 steps for
+ * LITTLE).
+ * Exynos5420 has less OPPs and reversed
+ * numbering of CPUs (big/LITTLE) so this
+ * would not match.
+ */
+ map5 {
+ trip = <&cpu_alert4>;
+ cooling-device = <&cpu0 7 7>;
+ };
+ map6 {
+ trip = <&cpu_alert4>;
+ cooling-device = <&cpu4 11 11>;
+ };
};
};
};
--
2.5.0
[toc] | [next] | [standalone]
| From | Anand Moon <linux.amoon@gmail.com> |
|---|---|
| Date | 2016-02-17 21:00 +0100 |
| Message-ID | <r3gqv-2DK-13@gated-at.bofh.it> |
| In reply to | #1336086 |
Hi Krzysztof,
On 17 February 2016 at 12:25, Krzysztof Kozlowski
<k.kozlowski@samsung.com> wrote:
> After adding cpufreq-dt support to Exynos542x, the Odroid XU3-Lite can
> be easily overheated when launching eight CPU-intensive tasks:
> thermal thermal_zone3: critical temperature reached(121 C),shutting down
>
> This seems to be specific to Odroid XU3-Lite board which officially
> supports lower frequencies than regular XU3 or XU4. When working at
> maximum CPU speed (1800 MHz big and 1300 MHz LITTLE) in warmer place for
> longer time, the fan fails to cool down the board and it reaches
> critical temperature.
>
> Add CPU cooling to Exynos5422/5800 to fix this issue. When reaching 95
> degrees of Celsius, the board will slow down by 3 steps (around
> 1400/1000 MHz). When reaching 110 degrees of Celsius go to 600 MHz.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> ---
> arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi | 41 +++++++++++++++++++++++++++
> 1 file changed, 41 insertions(+)
>
> diff --git a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
> index 2b289d7c0d13..66073ce29aee 100644
> --- a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
> +++ b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
> @@ -34,6 +34,16 @@
> hysteresis = <5000>; /* millicelsius */
> type = "active";
> };
> + cpu_alert3: cpu-alert-3 {
> + temperature = <95000>; /* millicelsius */
> + hysteresis = <5000>; /* millicelsius */
> + type = "passive";
> + };
> + cpu_alert4: cpu-alert-4 {
> + temperature = <110000>; /* millicelsius */
> + hysteresis = <5000>; /* millicelsius */
> + type = "passive";
> + };
> cpu_crit0: cpu-crit-0 {
> temperature = <120000>; /* millicelsius */
> hysteresis = <0>; /* millicelsius */
> @@ -53,6 +63,37 @@
> trip = <&cpu_alert2>;
> cooling-device = <&fan0 2 3>;
> };
> +
> + /*
> + * When reaching cpu_alert3, reduce CPU
> + * by 3 steps. On Exynos5422/5800 that would
> + * be: 1400 MHz and 1000 MHz.
> + */
> + map3 {
> + trip = <&cpu_alert3>;
> + cooling-device = <&cpu0 3 3>;
> + };
> + map4 {
> + trip = <&cpu_alert3>;
> + cooling-device = <&cpu4 3 3>;
> + };
> +
> + /*
> + * When reaching cpu_alert4, reduce CPU
> + * to 600 MHz (11 steps for big, 7 steps for
> + * LITTLE).
> + * Exynos5420 has less OPPs and reversed
> + * numbering of CPUs (big/LITTLE) so this
> + * would not match.
> + */
> + map5 {
> + trip = <&cpu_alert4>;
> + cooling-device = <&cpu0 7 7>;
> + };
> + map6 {
> + trip = <&cpu_alert4>;
> + cooling-device = <&cpu4 11 11>;
> + };
> };
> };
> };
> --
> 2.5.0
>
could you append this patch with following changes.
diff --git a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
index 66073ce..4e72637 100644
--- a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
+++ b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
@@ -16,8 +16,8 @@
thermal-zones {
cpu0_thermal: cpu0-thermal {
thermal-sensors = <&tmu_cpu0 0>;
- polling-delay-passive = <0>;
- polling-delay = <0>;
+ polling-delay-passive = <250>; /* milliseconds */
+ polling-delay = <500>; /* milliseconds */
trips {
cpu_alert0: cpu-alert-0 {
temperature = <50000>; /*
millicelsius */
---
On running linaro pm-qa diagnostic tool
----------------------------------------------------------
thermal_01.28: checking 'thermal_zone2'/'trip_point_2_temp' ='110000'... Ok
thermal_01.29: checking 'cdev0_trip_point' exists in
'/sys/devices/virtual/thermal/thermal_zone0'... Ok
thermal_01.30: checking 'thermal_zone0/cdev0_trip_point' valid binding... Ok
thermal_01.31: checking 'cdev4_trip_point' exists in
'/sys/devices/virtual/thermal/thermal_zone0'... Ok
thermal_01.32: checking 'thermal_zone0/cdev4_trip_point' valid binding... Err
thermal_01.33: checking 'cdev4_trip_point' exists in
'/sys/devices/virtual/thermal/thermal_zone0'... Ok
thermal_01.34: checking 'thermal_zone0/cdev4_trip_point' valid binding... Err
thermal_01.35: checking 'cdev4_trip_point' exists in
'/sys/devices/virtual/thermal/thermal_zone0'... Ok
thermal_01.36: checking 'thermal_zone0/cdev4_trip_point' valid binding... Err
thermal_01.37: checking 'cdev4_trip_point' exists in
'/sys/devices/virtual/thermal/thermal_zone0'... Ok
thermal_01.38: checking 'thermal_zone0/cdev4_trip_point' valid binding... Err
thermal_01: fail
-------------------------------------------------------
I also got lot's of error.
root@odroidxu4l:~# cpu[ 3050.847663] cpu cpu4: Failed to find dev_opp: -19
[ 3171.640836] cpu cpu4: device_opp_debug_create_link: Failed to create link
[ 3171.646197] cpu cpu4: _add_list_dev: Failed to register opp debugfs (-12)
[ 3171.653574] cpu cpu7: device_opp_debug_create_link: Failed to create link
[ 3171.659752] cpu cpu7: _add_list_dev: Failed to register opp debugfs (-12)
[ 3171.697011] cpu cpu5: cpufreq_init: failed to get clk: -2
[ 3171.732505] cpu cpu6: cpufreq_init: failed to get clk: -2
[ 3171.768160] cpu cpu7: cpufreq_init: failed to get clk: -2
Tested on Odroid-XU4
Reviewed-by: Anand Moon <linux.amoon@gmail.com>
Tested-by: Anand Moon <linux.amoon@gmail.com>
Best Regards
-Anand Moon
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[toc] | [prev] | [next] | [standalone]
| From | Krzysztof Kozlowski <k.kozlowski@samsung.com> |
|---|---|
| Date | 2016-02-18 02:50 +0100 |
| Message-ID | <r3lTc-6Da-19@gated-at.bofh.it> |
| In reply to | #1336712 |
On 18.02.2016 04:53, Anand Moon wrote:
> Hi Krzysztof,
>
> On 17 February 2016 at 12:25, Krzysztof Kozlowski
> <k.kozlowski@samsung.com> wrote:
>> After adding cpufreq-dt support to Exynos542x, the Odroid XU3-Lite can
>> be easily overheated when launching eight CPU-intensive tasks:
>> thermal thermal_zone3: critical temperature reached(121 C),shutting down
>>
>> This seems to be specific to Odroid XU3-Lite board which officially
>> supports lower frequencies than regular XU3 or XU4. When working at
>> maximum CPU speed (1800 MHz big and 1300 MHz LITTLE) in warmer place for
>> longer time, the fan fails to cool down the board and it reaches
>> critical temperature.
>>
>> Add CPU cooling to Exynos5422/5800 to fix this issue. When reaching 95
>> degrees of Celsius, the board will slow down by 3 steps (around
>> 1400/1000 MHz). When reaching 110 degrees of Celsius go to 600 MHz.
>>
>> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>> ---
>> arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi | 41 +++++++++++++++++++++++++++
>> 1 file changed, 41 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
>> index 2b289d7c0d13..66073ce29aee 100644
>> --- a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
>> +++ b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
>> @@ -34,6 +34,16 @@
>> hysteresis = <5000>; /* millicelsius */
>> type = "active";
>> };
>> + cpu_alert3: cpu-alert-3 {
>> + temperature = <95000>; /* millicelsius */
>> + hysteresis = <5000>; /* millicelsius */
>> + type = "passive";
>> + };
>> + cpu_alert4: cpu-alert-4 {
>> + temperature = <110000>; /* millicelsius */
>> + hysteresis = <5000>; /* millicelsius */
>> + type = "passive";
>> + };
>> cpu_crit0: cpu-crit-0 {
>> temperature = <120000>; /* millicelsius */
>> hysteresis = <0>; /* millicelsius */
>> @@ -53,6 +63,37 @@
>> trip = <&cpu_alert2>;
>> cooling-device = <&fan0 2 3>;
>> };
>> +
>> + /*
>> + * When reaching cpu_alert3, reduce CPU
>> + * by 3 steps. On Exynos5422/5800 that would
>> + * be: 1400 MHz and 1000 MHz.
>> + */
>> + map3 {
>> + trip = <&cpu_alert3>;
>> + cooling-device = <&cpu0 3 3>;
>> + };
>> + map4 {
>> + trip = <&cpu_alert3>;
>> + cooling-device = <&cpu4 3 3>;
>> + };
>> +
>> + /*
>> + * When reaching cpu_alert4, reduce CPU
>> + * to 600 MHz (11 steps for big, 7 steps for
>> + * LITTLE).
>> + * Exynos5420 has less OPPs and reversed
>> + * numbering of CPUs (big/LITTLE) so this
>> + * would not match.
>> + */
>> + map5 {
>> + trip = <&cpu_alert4>;
>> + cooling-device = <&cpu0 7 7>;
>> + };
>> + map6 {
>> + trip = <&cpu_alert4>;
>> + cooling-device = <&cpu4 11 11>;
>> + };
>> };
>> };
>> };
>> --
>> 2.5.0
>>
>
> could you append this patch with following changes.
Could you describe why?
> diff --git a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
> b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
> index 66073ce..4e72637 100644
> --- a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
> +++ b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
> @@ -16,8 +16,8 @@
> thermal-zones {
> cpu0_thermal: cpu0-thermal {
> thermal-sensors = <&tmu_cpu0 0>;
> - polling-delay-passive = <0>;
> - polling-delay = <0>;
> + polling-delay-passive = <250>; /* milliseconds */
> + polling-delay = <500>; /* milliseconds */
> trips {
> cpu_alert0: cpu-alert-0 {
> temperature = <50000>; /*
> millicelsius */
> ---
> On running linaro pm-qa diagnostic tool
> ----------------------------------------------------------
>
> thermal_01.28: checking 'thermal_zone2'/'trip_point_2_temp' ='110000'... Ok
> thermal_01.29: checking 'cdev0_trip_point' exists in
> '/sys/devices/virtual/thermal/thermal_zone0'... Ok
> thermal_01.30: checking 'thermal_zone0/cdev0_trip_point' valid binding... Ok
> thermal_01.31: checking 'cdev4_trip_point' exists in
> '/sys/devices/virtual/thermal/thermal_zone0'... Ok
> thermal_01.32: checking 'thermal_zone0/cdev4_trip_point' valid binding... Err
> thermal_01.33: checking 'cdev4_trip_point' exists in
> '/sys/devices/virtual/thermal/thermal_zone0'... Ok
> thermal_01.34: checking 'thermal_zone0/cdev4_trip_point' valid binding... Err
> thermal_01.35: checking 'cdev4_trip_point' exists in
> '/sys/devices/virtual/thermal/thermal_zone0'... Ok
> thermal_01.36: checking 'thermal_zone0/cdev4_trip_point' valid binding... Err
> thermal_01.37: checking 'cdev4_trip_point' exists in
> '/sys/devices/virtual/thermal/thermal_zone0'... Ok
> thermal_01.38: checking 'thermal_zone0/cdev4_trip_point' valid binding... Err
>
> thermal_01: fail
> -------------------------------------------------------
> I also got lot's of error.
>
> root@odroidxu4l:~# cpu[ 3050.847663] cpu cpu4: Failed to find dev_opp: -19
> [ 3171.640836] cpu cpu4: device_opp_debug_create_link: Failed to create link
> [ 3171.646197] cpu cpu4: _add_list_dev: Failed to register opp debugfs (-12)
> [ 3171.653574] cpu cpu7: device_opp_debug_create_link: Failed to create link
> [ 3171.659752] cpu cpu7: _add_list_dev: Failed to register opp debugfs (-12)
> [ 3171.697011] cpu cpu5: cpufreq_init: failed to get clk: -2
> [ 3171.732505] cpu cpu6: cpufreq_init: failed to get clk: -2
> [ 3171.768160] cpu cpu7: cpufreq_init: failed to get clk: -2
>
> Tested on Odroid-XU4
>
> Reviewed-by: Anand Moon <linux.amoon@gmail.com>
> Tested-by: Anand Moon <linux.amoon@gmail.com>
The patch is not sufficient. It does not work the way it should...
BTW, I found the issue. The order of trip points in DT:
thermal_zone0/trip_point_0_hyst:5000
thermal_zone0/trip_point_0_temp:50000
thermal_zone0/trip_point_0_type:active
thermal_zone0/trip_point_1_hyst:5000
thermal_zone0/trip_point_1_temp:60000
thermal_zone0/trip_point_1_type:active
thermal_zone0/trip_point_2_hyst:5000
thermal_zone0/trip_point_2_temp:70000
thermal_zone0/trip_point_2_type:active
thermal_zone0/trip_point_3_hyst:0
thermal_zone0/trip_point_3_temp:120000 <---- this should be last one!
thermal_zone0/trip_point_3_type:critical
thermal_zone0/trip_point_4_hyst:5000
thermal_zone0/trip_point_4_temp:90000
thermal_zone0/trip_point_4_type:passive
thermal_zone0/trip_point_5_hyst:5000
thermal_zone0/trip_point_5_temp:110000
thermal_zone0/trip_point_5_type:passive
After fixing the order in DT, the cpu cooler starts working.
Best regards,
Krzysztof
[toc] | [prev] | [next] | [standalone]
| From | Viresh Kumar <viresh.kumar@linaro.org> |
|---|---|
| Date | 2016-02-18 03:40 +0100 |
| Subject | Re: [RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load |
| Message-ID | <r3mFA-7hh-19@gated-at.bofh.it> |
| In reply to | #1336958 |
On 18-02-16, 10:47, Krzysztof Kozlowski wrote: > On 18.02.2016 04:53, Anand Moon wrote: > > I also got lot's of error. > > > > root@odroidxu4l:~# cpu[ 3050.847663] cpu cpu4: Failed to find dev_opp: -19 > > [ 3171.640836] cpu cpu4: device_opp_debug_create_link: Failed to create link > > [ 3171.646197] cpu cpu4: _add_list_dev: Failed to register opp debugfs (-12) > > [ 3171.653574] cpu cpu7: device_opp_debug_create_link: Failed to create link > > [ 3171.659752] cpu cpu7: _add_list_dev: Failed to register opp debugfs (-12) > > [ 3171.697011] cpu cpu5: cpufreq_init: failed to get clk: -2 > > [ 3171.732505] cpu cpu6: cpufreq_init: failed to get clk: -2 > > [ 3171.768160] cpu cpu7: cpufreq_init: failed to get clk: -2 > > > > Tested on Odroid-XU4 > > > > Reviewed-by: Anand Moon <linux.amoon@gmail.com> > > Tested-by: Anand Moon <linux.amoon@gmail.com> What was this Tested-by supposed to mean? You got errors out there ... > The patch is not sufficient. It does not work the way it should... > > BTW, I found the issue. The order of trip points in DT: > thermal_zone0/trip_point_0_hyst:5000 > thermal_zone0/trip_point_0_temp:50000 > thermal_zone0/trip_point_0_type:active > thermal_zone0/trip_point_1_hyst:5000 > thermal_zone0/trip_point_1_temp:60000 > thermal_zone0/trip_point_1_type:active > thermal_zone0/trip_point_2_hyst:5000 > thermal_zone0/trip_point_2_temp:70000 > thermal_zone0/trip_point_2_type:active > thermal_zone0/trip_point_3_hyst:0 > thermal_zone0/trip_point_3_temp:120000 <---- this should be last one! > thermal_zone0/trip_point_3_type:critical > thermal_zone0/trip_point_4_hyst:5000 > thermal_zone0/trip_point_4_temp:90000 > thermal_zone0/trip_point_4_type:passive > thermal_zone0/trip_point_5_hyst:5000 > thermal_zone0/trip_point_5_temp:110000 > thermal_zone0/trip_point_5_type:passive > > After fixing the order in DT, the cpu cooler starts working. Ahh, nice. -- viresh
[toc] | [prev] | [next] | [standalone]
| From | Anand Moon <linux.amoon@gmail.com> |
|---|---|
| Date | 2016-02-18 04:00 +0100 |
| Message-ID | <r3mYW-7p0-5@gated-at.bofh.it> |
| In reply to | #1336989 |
Hi Viresh, On 18 February 2016 at 08:06, Viresh Kumar <viresh.kumar@linaro.org> wrote: > On 18-02-16, 10:47, Krzysztof Kozlowski wrote: >> On 18.02.2016 04:53, Anand Moon wrote: >> > I also got lot's of error. >> > >> > root@odroidxu4l:~# cpu[ 3050.847663] cpu cpu4: Failed to find dev_opp: -19 >> > [ 3171.640836] cpu cpu4: device_opp_debug_create_link: Failed to create link >> > [ 3171.646197] cpu cpu4: _add_list_dev: Failed to register opp debugfs (-12) >> > [ 3171.653574] cpu cpu7: device_opp_debug_create_link: Failed to create link >> > [ 3171.659752] cpu cpu7: _add_list_dev: Failed to register opp debugfs (-12) >> > [ 3171.697011] cpu cpu5: cpufreq_init: failed to get clk: -2 >> > [ 3171.732505] cpu cpu6: cpufreq_init: failed to get clk: -2 >> > [ 3171.768160] cpu cpu7: cpufreq_init: failed to get clk: -2 >> > >> > Tested on Odroid-XU4 >> > >> > Reviewed-by: Anand Moon <linux.amoon@gmail.com> >> > Tested-by: Anand Moon <linux.amoon@gmail.com> > > What was this Tested-by supposed to mean? You got errors out there ... > I had done some stress testing, as pointed by Krzysztof. I got myself in two minds on this part, please don't consider the Tested-by and Reviewed-by part. Thanks for pointing out. -Anand Moon >> The patch is not sufficient. It does not work the way it should... >> >> BTW, I found the issue. The order of trip points in DT: >> thermal_zone0/trip_point_0_hyst:5000 >> thermal_zone0/trip_point_0_temp:50000 >> thermal_zone0/trip_point_0_type:active >> thermal_zone0/trip_point_1_hyst:5000 >> thermal_zone0/trip_point_1_temp:60000 >> thermal_zone0/trip_point_1_type:active >> thermal_zone0/trip_point_2_hyst:5000 >> thermal_zone0/trip_point_2_temp:70000 >> thermal_zone0/trip_point_2_type:active >> thermal_zone0/trip_point_3_hyst:0 >> thermal_zone0/trip_point_3_temp:120000 <---- this should be last one! >> thermal_zone0/trip_point_3_type:critical >> thermal_zone0/trip_point_4_hyst:5000 >> thermal_zone0/trip_point_4_temp:90000 >> thermal_zone0/trip_point_4_type:passive >> thermal_zone0/trip_point_5_hyst:5000 >> thermal_zone0/trip_point_5_temp:110000 >> thermal_zone0/trip_point_5_type:passive >> >> After fixing the order in DT, the cpu cooler starts working. > > Ahh, nice. > > -- > viresh
[toc] | [prev] | [next] | [standalone]
| From | Krzysztof Kozlowski <k.kozlowski@samsung.com> |
|---|---|
| Date | 2016-02-18 05:50 +0100 |
| Message-ID | <r3oHo-fk-7@gated-at.bofh.it> |
| In reply to | #1336989 |
On 18.02.2016 11:36, Viresh Kumar wrote: >> >> BTW, I found the issue. The order of trip points in DT: >> thermal_zone0/trip_point_0_hyst:5000 >> thermal_zone0/trip_point_0_temp:50000 >> thermal_zone0/trip_point_0_type:active >> thermal_zone0/trip_point_1_hyst:5000 >> thermal_zone0/trip_point_1_temp:60000 >> thermal_zone0/trip_point_1_type:active >> thermal_zone0/trip_point_2_hyst:5000 >> thermal_zone0/trip_point_2_temp:70000 >> thermal_zone0/trip_point_2_type:active >> thermal_zone0/trip_point_3_hyst:0 >> thermal_zone0/trip_point_3_temp:120000 <---- this should be last one! >> thermal_zone0/trip_point_3_type:critical >> thermal_zone0/trip_point_4_hyst:5000 >> thermal_zone0/trip_point_4_temp:90000 >> thermal_zone0/trip_point_4_type:passive >> thermal_zone0/trip_point_5_hyst:5000 >> thermal_zone0/trip_point_5_temp:110000 >> thermal_zone0/trip_point_5_type:passive >> >> After fixing the order in DT, the cpu cooler starts working. > > Ahh, nice. Damn, not entirely. I almost fried my Odroid (it survived 130 degrees of C)... The TMU supports only 4 trip points, so when I added two new trip points and reordered them... the last two (including critical) was not receiving interrupts. Polling mode is needed. I'll sent some patches soon... BR, Krzysztof
[toc] | [prev] | [next] | [standalone]
| From | Marek Szyprowski <m.szyprowski@samsung.com> |
|---|---|
| Date | 2016-02-18 11:00 +0100 |
| Message-ID | <r3txp-3CY-23@gated-at.bofh.it> |
| In reply to | #1337024 |
Hello, On 2016-02-18 05:42, Krzysztof Kozlowski wrote: > On 18.02.2016 11:36, Viresh Kumar wrote: >>> BTW, I found the issue. The order of trip points in DT: >>> thermal_zone0/trip_point_0_hyst:5000 >>> thermal_zone0/trip_point_0_temp:50000 >>> thermal_zone0/trip_point_0_type:active >>> thermal_zone0/trip_point_1_hyst:5000 >>> thermal_zone0/trip_point_1_temp:60000 >>> thermal_zone0/trip_point_1_type:active >>> thermal_zone0/trip_point_2_hyst:5000 >>> thermal_zone0/trip_point_2_temp:70000 >>> thermal_zone0/trip_point_2_type:active >>> thermal_zone0/trip_point_3_hyst:0 >>> thermal_zone0/trip_point_3_temp:120000 <---- this should be last one! >>> thermal_zone0/trip_point_3_type:critical >>> thermal_zone0/trip_point_4_hyst:5000 >>> thermal_zone0/trip_point_4_temp:90000 >>> thermal_zone0/trip_point_4_type:passive >>> thermal_zone0/trip_point_5_hyst:5000 >>> thermal_zone0/trip_point_5_temp:110000 >>> thermal_zone0/trip_point_5_type:passive >>> >>> After fixing the order in DT, the cpu cooler starts working. >> Ahh, nice. > Damn, not entirely. I almost fried my Odroid (it survived 130 degrees of > C)... The TMU supports only 4 trip points, so when I added two new trip > points and reordered them... the last two (including critical) was not > receiving interrupts. > > Polling mode is needed. I'll sent some patches soon... Instead of polling the driver should simply use some dynamic window for the nearest temperature ranges and reconfigure it when interrupt of occurs. Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland
[toc] | [prev] | [next] | [standalone]
| From | Krzysztof Kozlowski <k.kozlowski@samsung.com> |
|---|---|
| Date | 2016-02-19 01:00 +0100 |
| Message-ID | <r3GEi-4LS-1@gated-at.bofh.it> |
| In reply to | #1337218 |
On 18.02.2016 18:59, Marek Szyprowski wrote: > Hello, > > On 2016-02-18 05:42, Krzysztof Kozlowski wrote: >> On 18.02.2016 11:36, Viresh Kumar wrote: >>>> BTW, I found the issue. The order of trip points in DT: >>>> thermal_zone0/trip_point_0_hyst:5000 >>>> thermal_zone0/trip_point_0_temp:50000 >>>> thermal_zone0/trip_point_0_type:active >>>> thermal_zone0/trip_point_1_hyst:5000 >>>> thermal_zone0/trip_point_1_temp:60000 >>>> thermal_zone0/trip_point_1_type:active >>>> thermal_zone0/trip_point_2_hyst:5000 >>>> thermal_zone0/trip_point_2_temp:70000 >>>> thermal_zone0/trip_point_2_type:active >>>> thermal_zone0/trip_point_3_hyst:0 >>>> thermal_zone0/trip_point_3_temp:120000 <---- this should be last >>>> one! >>>> thermal_zone0/trip_point_3_type:critical >>>> thermal_zone0/trip_point_4_hyst:5000 >>>> thermal_zone0/trip_point_4_temp:90000 >>>> thermal_zone0/trip_point_4_type:passive >>>> thermal_zone0/trip_point_5_hyst:5000 >>>> thermal_zone0/trip_point_5_temp:110000 >>>> thermal_zone0/trip_point_5_type:passive >>>> >>>> After fixing the order in DT, the cpu cooler starts working. >>> Ahh, nice. >> Damn, not entirely. I almost fried my Odroid (it survived 130 degrees of >> C)... The TMU supports only 4 trip points, so when I added two new trip >> points and reordered them... the last two (including critical) was not >> receiving interrupts. >> >> Polling mode is needed. I'll sent some patches soon... > > Instead of polling the driver should simply use some dynamic window for > the nearest temperature ranges and reconfigure it when interrupt of occurs. Thanks for feedback, Marek! First of all the polling happens only when initial trip point for passive cooling is reached (70 degrees C). This fortunately reduces the polling overhead. Yours idea seems interesting... but driver does not support it now, does it? I can put this on TODO list, maybe someone will extend the exynos thermal driver. Best regards, Krzysztof
[toc] | [prev] | [next] | [standalone]
| From | Anand Moon <linux.amoon@gmail.com> |
|---|---|
| Date | 2016-02-18 04:20 +0100 |
| Message-ID | <r3nii-7S0-7@gated-at.bofh.it> |
| In reply to | #1336958 |
Hi Krzysztof
On 18 February 2016 at 07:17, Krzysztof Kozlowski
<k.kozlowski@samsung.com> wrote:
> On 18.02.2016 04:53, Anand Moon wrote:
>> Hi Krzysztof,
>>
>> On 17 February 2016 at 12:25, Krzysztof Kozlowski
>> <k.kozlowski@samsung.com> wrote:
>>> After adding cpufreq-dt support to Exynos542x, the Odroid XU3-Lite can
>>> be easily overheated when launching eight CPU-intensive tasks:
>>> thermal thermal_zone3: critical temperature reached(121 C),shutting down
>>>
>>> This seems to be specific to Odroid XU3-Lite board which officially
>>> supports lower frequencies than regular XU3 or XU4. When working at
>>> maximum CPU speed (1800 MHz big and 1300 MHz LITTLE) in warmer place for
>>> longer time, the fan fails to cool down the board and it reaches
>>> critical temperature.
>>>
>>> Add CPU cooling to Exynos5422/5800 to fix this issue. When reaching 95
>>> degrees of Celsius, the board will slow down by 3 steps (around
>>> 1400/1000 MHz). When reaching 110 degrees of Celsius go to 600 MHz.
>>>
>>> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>>> ---
>>> arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi | 41 +++++++++++++++++++++++++++
>>> 1 file changed, 41 insertions(+)
>>>
>>> diff --git a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
>>> index 2b289d7c0d13..66073ce29aee 100644
>>> --- a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
>>> +++ b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
>>> @@ -34,6 +34,16 @@
>>> hysteresis = <5000>; /* millicelsius */
>>> type = "active";
>>> };
>>> + cpu_alert3: cpu-alert-3 {
>>> + temperature = <95000>; /* millicelsius */
>>> + hysteresis = <5000>; /* millicelsius */
>>> + type = "passive";
>>> + };
>>> + cpu_alert4: cpu-alert-4 {
>>> + temperature = <110000>; /* millicelsius */
>>> + hysteresis = <5000>; /* millicelsius */
>>> + type = "passive";
>>> + };
>>> cpu_crit0: cpu-crit-0 {
>>> temperature = <120000>; /* millicelsius */
>>> hysteresis = <0>; /* millicelsius */
>>> @@ -53,6 +63,37 @@
>>> trip = <&cpu_alert2>;
>>> cooling-device = <&fan0 2 3>;
>>> };
>>> +
>>> + /*
>>> + * When reaching cpu_alert3, reduce CPU
>>> + * by 3 steps. On Exynos5422/5800 that would
>>> + * be: 1400 MHz and 1000 MHz.
>>> + */
>>> + map3 {
>>> + trip = <&cpu_alert3>;
>>> + cooling-device = <&cpu0 3 3>;
>>> + };
>>> + map4 {
>>> + trip = <&cpu_alert3>;
>>> + cooling-device = <&cpu4 3 3>;
>>> + };
>>> +
>>> + /*
>>> + * When reaching cpu_alert4, reduce CPU
>>> + * to 600 MHz (11 steps for big, 7 steps for
>>> + * LITTLE).
>>> + * Exynos5420 has less OPPs and reversed
>>> + * numbering of CPUs (big/LITTLE) so this
>>> + * would not match.
>>> + */
>>> + map5 {
>>> + trip = <&cpu_alert4>;
>>> + cooling-device = <&cpu0 7 7>;
>>> + };
>>> + map6 {
>>> + trip = <&cpu_alert4>;
>>> + cooling-device = <&cpu4 11 11>;
>>> + };
>>> };
>>> };
>>> };
>>> --
>>> 2.5.0
>>>
>>
>> could you append this patch with following changes.
>
> Could you describe why?
>
From the documentation.
Documentation/thermal/sysfs-api.txt
passive_delay: number of milliseconds to wait between polls when
performing passive cooling.
polling_delay: number of milliseconds to wait between polls when
checking whether trip points have been crossed (0 for interrupt
driven systems).
Exynos driver is interrupt driven so please ignore.
Best Regards.
-Anand Moon
>> diff --git a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
>> b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
>> index 66073ce..4e72637 100644
>> --- a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
>> +++ b/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi
>> @@ -16,8 +16,8 @@
>> thermal-zones {
>> cpu0_thermal: cpu0-thermal {
>> thermal-sensors = <&tmu_cpu0 0>;
>> - polling-delay-passive = <0>;
>> - polling-delay = <0>;
>> + polling-delay-passive = <250>; /* milliseconds */
>> + polling-delay = <500>; /* milliseconds */
>> trips {
>> cpu_alert0: cpu-alert-0 {
>> temperature = <50000>; /*
>> millicelsius */
>> ---
>> On running linaro pm-qa diagnostic tool
>> ----------------------------------------------------------
>>
>> thermal_01.28: checking 'thermal_zone2'/'trip_point_2_temp' ='110000'... Ok
>> thermal_01.29: checking 'cdev0_trip_point' exists in
>> '/sys/devices/virtual/thermal/thermal_zone0'... Ok
>> thermal_01.30: checking 'thermal_zone0/cdev0_trip_point' valid binding... Ok
>> thermal_01.31: checking 'cdev4_trip_point' exists in
>> '/sys/devices/virtual/thermal/thermal_zone0'... Ok
>> thermal_01.32: checking 'thermal_zone0/cdev4_trip_point' valid binding... Err
>> thermal_01.33: checking 'cdev4_trip_point' exists in
>> '/sys/devices/virtual/thermal/thermal_zone0'... Ok
>> thermal_01.34: checking 'thermal_zone0/cdev4_trip_point' valid binding... Err
>> thermal_01.35: checking 'cdev4_trip_point' exists in
>> '/sys/devices/virtual/thermal/thermal_zone0'... Ok
>> thermal_01.36: checking 'thermal_zone0/cdev4_trip_point' valid binding... Err
>> thermal_01.37: checking 'cdev4_trip_point' exists in
>> '/sys/devices/virtual/thermal/thermal_zone0'... Ok
>> thermal_01.38: checking 'thermal_zone0/cdev4_trip_point' valid binding... Err
>>
>> thermal_01: fail
>> -------------------------------------------------------
>> I also got lot's of error.
>>
>> root@odroidxu4l:~# cpu[ 3050.847663] cpu cpu4: Failed to find dev_opp: -19
>> [ 3171.640836] cpu cpu4: device_opp_debug_create_link: Failed to create link
>> [ 3171.646197] cpu cpu4: _add_list_dev: Failed to register opp debugfs (-12)
>> [ 3171.653574] cpu cpu7: device_opp_debug_create_link: Failed to create link
>> [ 3171.659752] cpu cpu7: _add_list_dev: Failed to register opp debugfs (-12)
>> [ 3171.697011] cpu cpu5: cpufreq_init: failed to get clk: -2
>> [ 3171.732505] cpu cpu6: cpufreq_init: failed to get clk: -2
>> [ 3171.768160] cpu cpu7: cpufreq_init: failed to get clk: -2
>>
>> Tested on Odroid-XU4
>>
>> Reviewed-by: Anand Moon <linux.amoon@gmail.com>
>> Tested-by: Anand Moon <linux.amoon@gmail.com>
>
> The patch is not sufficient. It does not work the way it should...
>
> BTW, I found the issue. The order of trip points in DT:
> thermal_zone0/trip_point_0_hyst:5000
> thermal_zone0/trip_point_0_temp:50000
> thermal_zone0/trip_point_0_type:active
> thermal_zone0/trip_point_1_hyst:5000
> thermal_zone0/trip_point_1_temp:60000
> thermal_zone0/trip_point_1_type:active
> thermal_zone0/trip_point_2_hyst:5000
> thermal_zone0/trip_point_2_temp:70000
> thermal_zone0/trip_point_2_type:active
> thermal_zone0/trip_point_3_hyst:0
> thermal_zone0/trip_point_3_temp:120000 <---- this should be last one!
> thermal_zone0/trip_point_3_type:critical
> thermal_zone0/trip_point_4_hyst:5000
> thermal_zone0/trip_point_4_temp:90000
> thermal_zone0/trip_point_4_type:passive
> thermal_zone0/trip_point_5_hyst:5000
> thermal_zone0/trip_point_5_temp:110000
> thermal_zone0/trip_point_5_type:passive
>
> After fixing the order in DT, the cpu cooler starts working.
>
> Best regards,
> Krzysztof
>
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web