Re: [PATCH 1/3] thermal: step_wise: fix: Prevent from binary overflow when trend is dropping
On Wed, 2014-09-24 at 10:27 +0200, Lukasz Majewski wrote:
> It turns out that some boards can have instance->lower greater than 0 and
> when thermal trend is dropping it results with next_target equal to -1.
>
> Since the next_target is defined as unsigned long it is interpreted as
> 0x and larger than instance->upper.
> As a result the next_target is set to instance->upper which ramps up to
> maximal cooling device target when the temperature is steadily decreasing.
>
> Signed-off-by: Lukasz Majewski
applied.
thanks,
rui
> ---
> drivers/thermal/step_wise.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/thermal/step_wise.c b/drivers/thermal/step_wise.c
> index 3b54c2c..fdd1f52 100644
> --- a/drivers/thermal/step_wise.c
> +++ b/drivers/thermal/step_wise.c
> @@ -77,7 +77,7 @@ static unsigned long get_target_state(struct
> thermal_instance *instance,
> next_target = instance->upper;
> break;
> case THERMAL_TREND_DROPPING:
> - if (cur_state == instance->lower) {
> + if (cur_state <= instance->lower) {
> if (!throttle)
> next_target = THERMAL_NO_TARGET;
> } else {
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 1/3] thermal: step_wise: fix: Prevent from binary overflow when trend is dropping
On Wed, 2014-09-24 at 10:27 +0200, Lukasz Majewski wrote:
It turns out that some boards can have instance-lower greater than 0 and
when thermal trend is dropping it results with next_target equal to -1.
Since the next_target is defined as unsigned long it is interpreted as
0x and larger than instance-upper.
As a result the next_target is set to instance-upper which ramps up to
maximal cooling device target when the temperature is steadily decreasing.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
applied.
thanks,
rui
---
drivers/thermal/step_wise.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/step_wise.c b/drivers/thermal/step_wise.c
index 3b54c2c..fdd1f52 100644
--- a/drivers/thermal/step_wise.c
+++ b/drivers/thermal/step_wise.c
@@ -77,7 +77,7 @@ static unsigned long get_target_state(struct
thermal_instance *instance,
next_target = instance-upper;
break;
case THERMAL_TREND_DROPPING:
- if (cur_state == instance-lower) {
+ if (cur_state = instance-lower) {
if (!throttle)
next_target = THERMAL_NO_TARGET;
} else {
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 1/3] thermal: step_wise: fix: Prevent from binary overflow when trend is dropping
Hi Eduardo,
> Hello Lukasz,
>
> On Wed, Sep 24, 2014 at 10:27:10AM +0200, Lukasz Majewski wrote:
> > It turns out that some boards can have instance->lower greater than
> > 0 and when thermal trend is dropping it results with next_target
> > equal to -1.
> >
> > Since the next_target is defined as unsigned long it is interpreted
> > as 0x and larger than instance->upper.
> > As a result the next_target is set to instance->upper which ramps
> > up to maximal cooling device target when the temperature is
> > steadily decreasing.
> >
>
> Thanks for finding a problem and sending a fix.
>
> Can you please explain a little more on how next_target reaches -1
> when lower is greater than 0?
During testing I've created a fan based cooling device with
"instance->lower" = 1 and "instance->upper" = 3.
On the system the ordinary cpu_cooling device is also present.
With step_wise.c it happens that at "THERMAL_TREND_DROPPING" the
cur_state = 0, so the first if condition is false (line 80) and
cur_state, which is defined as unsigned long, is decremented. This
means that next_target equals to 0x because it also is defined
as unsigned long.
Such value is apparently bigger than "instance->upper" (line 85) and
therefore the maximal cooling state is chosen. As a result, even when
the thermal trend is dropping, the cooling device increase the cooling
state to maximum.
This behavior has been discovered during my work on adapting exynos
thermal driver to reuse the of-thermal. I will send patches for this
work after the weekend.
>
>
> > Signed-off-by: Lukasz Majewski
> > ---
> > drivers/thermal/step_wise.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/thermal/step_wise.c
> > b/drivers/thermal/step_wise.c index 3b54c2c..fdd1f52 100644
> > --- a/drivers/thermal/step_wise.c
> > +++ b/drivers/thermal/step_wise.c
> > @@ -77,7 +77,7 @@ static unsigned long get_target_state(struct
> > thermal_instance *instance, next_target = instance->upper;
> > break;
> > case THERMAL_TREND_DROPPING:
> > - if (cur_state == instance->lower) {
> > + if (cur_state <= instance->lower) {
> > if (!throttle)
> > next_target = THERMAL_NO_TARGET;
> > } else {
> > --
> > 2.0.0.rc2
> >
>
>
> Eduardo
--
Best regards,
Lukasz Majewski
Samsung R Institute Poland (SRPOL) | Linux Platform Group
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 1/3] thermal: step_wise: fix: Prevent from binary overflow when trend is dropping
Hi Eduardo,
Hello Lukasz,
On Wed, Sep 24, 2014 at 10:27:10AM +0200, Lukasz Majewski wrote:
It turns out that some boards can have instance-lower greater than
0 and when thermal trend is dropping it results with next_target
equal to -1.
Since the next_target is defined as unsigned long it is interpreted
as 0x and larger than instance-upper.
As a result the next_target is set to instance-upper which ramps
up to maximal cooling device target when the temperature is
steadily decreasing.
Thanks for finding a problem and sending a fix.
Can you please explain a little more on how next_target reaches -1
when lower is greater than 0?
During testing I've created a fan based cooling device with
instance-lower = 1 and instance-upper = 3.
On the system the ordinary cpu_cooling device is also present.
With step_wise.c it happens that at THERMAL_TREND_DROPPING the
cur_state = 0, so the first if condition is false (line 80) and
cur_state, which is defined as unsigned long, is decremented. This
means that next_target equals to 0x because it also is defined
as unsigned long.
Such value is apparently bigger than instance-upper (line 85) and
therefore the maximal cooling state is chosen. As a result, even when
the thermal trend is dropping, the cooling device increase the cooling
state to maximum.
This behavior has been discovered during my work on adapting exynos
thermal driver to reuse the of-thermal. I will send patches for this
work after the weekend.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/step_wise.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/step_wise.c
b/drivers/thermal/step_wise.c index 3b54c2c..fdd1f52 100644
--- a/drivers/thermal/step_wise.c
+++ b/drivers/thermal/step_wise.c
@@ -77,7 +77,7 @@ static unsigned long get_target_state(struct
thermal_instance *instance, next_target = instance-upper;
break;
case THERMAL_TREND_DROPPING:
- if (cur_state == instance-lower) {
+ if (cur_state = instance-lower) {
if (!throttle)
next_target = THERMAL_NO_TARGET;
} else {
--
2.0.0.rc2
Eduardo
--
Best regards,
Lukasz Majewski
Samsung RD Institute Poland (SRPOL) | Linux Platform Group
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 1/3] thermal: step_wise: fix: Prevent from binary overflow when trend is dropping
Hello Lukasz,
On Wed, Sep 24, 2014 at 10:27:10AM +0200, Lukasz Majewski wrote:
> It turns out that some boards can have instance->lower greater than 0 and
> when thermal trend is dropping it results with next_target equal to -1.
>
> Since the next_target is defined as unsigned long it is interpreted as
> 0x and larger than instance->upper.
> As a result the next_target is set to instance->upper which ramps up to
> maximal cooling device target when the temperature is steadily decreasing.
>
Thanks for finding a problem and sending a fix.
Can you please explain a little more on how next_target reaches -1 when
lower is greater than 0?
> Signed-off-by: Lukasz Majewski
> ---
> drivers/thermal/step_wise.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/thermal/step_wise.c b/drivers/thermal/step_wise.c
> index 3b54c2c..fdd1f52 100644
> --- a/drivers/thermal/step_wise.c
> +++ b/drivers/thermal/step_wise.c
> @@ -77,7 +77,7 @@ static unsigned long get_target_state(struct
> thermal_instance *instance,
> next_target = instance->upper;
> break;
> case THERMAL_TREND_DROPPING:
> - if (cur_state == instance->lower) {
> + if (cur_state <= instance->lower) {
> if (!throttle)
> next_target = THERMAL_NO_TARGET;
> } else {
> --
> 2.0.0.rc2
>
Eduardo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 1/3] thermal: step_wise: fix: Prevent from binary overflow when trend is dropping
Hello Lukasz,
On Wed, Sep 24, 2014 at 10:27:10AM +0200, Lukasz Majewski wrote:
It turns out that some boards can have instance-lower greater than 0 and
when thermal trend is dropping it results with next_target equal to -1.
Since the next_target is defined as unsigned long it is interpreted as
0x and larger than instance-upper.
As a result the next_target is set to instance-upper which ramps up to
maximal cooling device target when the temperature is steadily decreasing.
Thanks for finding a problem and sending a fix.
Can you please explain a little more on how next_target reaches -1 when
lower is greater than 0?
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/step_wise.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/step_wise.c b/drivers/thermal/step_wise.c
index 3b54c2c..fdd1f52 100644
--- a/drivers/thermal/step_wise.c
+++ b/drivers/thermal/step_wise.c
@@ -77,7 +77,7 @@ static unsigned long get_target_state(struct
thermal_instance *instance,
next_target = instance-upper;
break;
case THERMAL_TREND_DROPPING:
- if (cur_state == instance-lower) {
+ if (cur_state = instance-lower) {
if (!throttle)
next_target = THERMAL_NO_TARGET;
} else {
--
2.0.0.rc2
Eduardo
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 1/3] thermal: step_wise: fix: Prevent from binary overflow when trend is dropping
It turns out that some boards can have instance->lower greater than 0 and
when thermal trend is dropping it results with next_target equal to -1.
Since the next_target is defined as unsigned long it is interpreted as
0x and larger than instance->upper.
As a result the next_target is set to instance->upper which ramps up to
maximal cooling device target when the temperature is steadily decreasing.
Signed-off-by: Lukasz Majewski
---
drivers/thermal/step_wise.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/step_wise.c b/drivers/thermal/step_wise.c
index 3b54c2c..fdd1f52 100644
--- a/drivers/thermal/step_wise.c
+++ b/drivers/thermal/step_wise.c
@@ -77,7 +77,7 @@ static unsigned long get_target_state(struct thermal_instance
*instance,
next_target = instance->upper;
break;
case THERMAL_TREND_DROPPING:
- if (cur_state == instance->lower) {
+ if (cur_state <= instance->lower) {
if (!throttle)
next_target = THERMAL_NO_TARGET;
} else {
--
2.0.0.rc2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 1/3] thermal: step_wise: fix: Prevent from binary overflow when trend is dropping
It turns out that some boards can have instance-lower greater than 0 and
when thermal trend is dropping it results with next_target equal to -1.
Since the next_target is defined as unsigned long it is interpreted as
0x and larger than instance-upper.
As a result the next_target is set to instance-upper which ramps up to
maximal cooling device target when the temperature is steadily decreasing.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/step_wise.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/step_wise.c b/drivers/thermal/step_wise.c
index 3b54c2c..fdd1f52 100644
--- a/drivers/thermal/step_wise.c
+++ b/drivers/thermal/step_wise.c
@@ -77,7 +77,7 @@ static unsigned long get_target_state(struct thermal_instance
*instance,
next_target = instance-upper;
break;
case THERMAL_TREND_DROPPING:
- if (cur_state == instance-lower) {
+ if (cur_state = instance-lower) {
if (!throttle)
next_target = THERMAL_NO_TARGET;
} else {
--
2.0.0.rc2
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
