linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "edubezval@gmail.com" <edubezval@gmail.com>,
	"Zhang, Rui" <rui.zhang@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCHv2 3/3] thermal: improve hot trip handling
Date: Wed, 16 Mar 2016 00:14:35 +0000	[thread overview]
Message-ID: <1458083515.4486.45.camel@intel.com> (raw)
In-Reply-To: <1450379609-7826-4-git-send-email-edubezval@gmail.com>

On Thu, 2015-12-17 at 11:13 -0800, Eduardo Valentin wrote:
> The idea is to add the choice to be notified only when temperature
> crosses trip points. The trip points affected are the non-passive
> trip points.
> 
> It will check last temperature and current temperature against
> the trip point temperature and its hysteresis.
> In case the check shows temperature has changed enought indicating
> a trip point crossing, a uevent will be sent to userspace.
> 
> The uevent contains the thermal zone type, the current temperature,
> the last temperature and the trip point in which the current
> temperature
> now resides.
> 
> The behavior of ops->notify() callback remains the same.
> 
IMO we need to handle also passive/active trips. I have some comments
here
https://patchwork.kernel.org/patch/8583171/

Thanks,
Srinivas

> Cc: Zhang Rui <rui.zhang@intel.com>
> Cc: linux-pm@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Eduardo Valentin <edubezval@gmail.com>
> ---
> V1->V2: none
> ---
>  drivers/thermal/thermal_core.c | 52
> ++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 52 insertions(+)
> 
> diff --git a/drivers/thermal/thermal_core.c
> b/drivers/thermal/thermal_core.c
> index a229c84..e0f1f4e 100644
> --- a/drivers/thermal/thermal_core.c
> +++ b/drivers/thermal/thermal_core.c
> @@ -423,6 +423,56 @@ static void handle_non_critical_trips(struct
> thermal_zone_device *tz,
>  		       def_governor->throttle(tz, trip);
>  }
>  
> +static void thermal_tripped_notify(struct thermal_zone_device *tz,
> +				   int trip, enum thermal_trip_type
> trip_type,
> +				   int trip_temp)
> +{
> +	char tuv_name[THERMAL_NAME_LENGTH + 15], tuv_temp[25],
> +		tuv_ltemp[25], tuv_trip[25], tuv_type[25];
> +	char *msg[6] = { tuv_name, tuv_temp, tuv_ltemp, tuv_trip,
> tuv_type,
> +			NULL };
> +	int upper_trip_hyst, upper_trip_temp, trip_hyst = 0;
> +	int ret = 0;
> +
> +	snprintf(tuv_name, sizeof(tuv_name), "THERMAL_ZONE=%s", tz-
> >type);
> +	snprintf(tuv_temp, sizeof(tuv_temp), "TEMP=%d", tz-
> >temperature);
> +	snprintf(tuv_ltemp, sizeof(tuv_ltemp), "LAST_TEMP=%d",
> +		 tz->last_temperature);
> +	snprintf(tuv_trip, sizeof(tuv_trip), "TRIP=%d", trip);
> +	snprintf(tuv_type, sizeof(tuv_type), "TRIP_TYPE=%d",
> trip_type);
> +
> +	mutex_lock(&tz->lock);
> +
> +	/* crossing up */
> +	if (tz->last_temperature < trip_temp && trip_temp < tz-
> >temperature)
> +		kobject_uevent_env(&tz->device.kobj, KOBJ_CHANGE,
> msg);
> +
> +	if (tz->ops->get_trip_hyst)
> +		tz->ops->get_trip_hyst(tz, trip, &trip_hyst);
> +
> +	/* crossing down, check for hyst */
> +	trip_temp -= trip_hyst;
> +	if (tz->last_temperature > trip_temp && trip_temp > tz-
> >temperature) {
> +		snprintf(tuv_trip, sizeof(tuv_trip), "TRIP=%d", trip
> - 1);
> +		kobject_uevent_env(&tz->device.kobj, KOBJ_CHANGE,
> msg);
> +	}
> +
> +	ret = tz->ops->get_trip_temp(tz, trip + 1,
> &upper_trip_temp);
> +	if (ret)
> +		goto unlock;
> +
> +	if (tz->ops->get_trip_hyst)
> +		tz->ops->get_trip_hyst(tz, trip + 1,
> &upper_trip_hyst);
> +
> +	upper_trip_temp -= upper_trip_hyst;
> +	if (tz->last_temperature > upper_trip_temp &&
> +	    upper_trip_temp > tz->temperature)
> +		kobject_uevent_env(&tz->device.kobj, KOBJ_CHANGE,
> msg);
> +
> +unlock:
> +	mutex_unlock(&tz->lock);
> +}
> +
>  static void handle_critical_trips(struct thermal_zone_device *tz,
>  				int trip, enum thermal_trip_type
> trip_type)
>  {
> @@ -430,6 +480,8 @@ static void handle_critical_trips(struct
> thermal_zone_device *tz,
>  
>  	tz->ops->get_trip_temp(tz, trip, &trip_temp);
>  
> +	thermal_tripped_notify(tz, trip, trip_type, trip_temp);
> +
>  	/* If we have not crossed the trip_temp, we do not care. */
>  	if (trip_temp <= 0 || tz->temperature < trip_temp)
>  		return;

      parent reply	other threads:[~2016-03-16  0:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 19:13 [PATCHv2 0/3] thermal: rework core to improve userspace interaction Eduardo Valentin
2015-12-17 19:13 ` [PATCHv2 1/3] thermal: setup monitor only once after handling trips Eduardo Valentin
2015-12-17 19:13 ` [PATCHv2 2/3] thermal: rework core to allow emul_temp to be treated as regular temp Eduardo Valentin
2016-03-16  0:09   ` Pandruvada, Srinivas
2015-12-17 19:13 ` [PATCHv2 3/3] thermal: improve hot trip handling Eduardo Valentin
2016-01-05  9:46   ` Geert Uytterhoeven
2016-02-03 23:24     ` Srikar Srimath Tirumala
2016-03-16  0:14   ` Pandruvada, Srinivas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1458083515.4486.45.camel@intel.com \
    --to=srinivas.pandruvada@intel.com \
    --cc=edubezval@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).