All of lore.kernel.org
 help / color / mirror / Atom feed
From: Caesar Wang <wxt@rock-chips.com>
To: Javi Merino <javi.merino@arm.com>
Cc: Caesar Wang <wxt@rock-chips.com>,
	huangtao@rock-chips.com, Jonathan Corbet <corbet@lwn.net>,
	Ni Wade <wni@nvidia.com>, Heiko Stuebner <heiko@sntech.de>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sascha Hauer <s.hauer@pengutronix.de>,
	dmitry.torokhov@gmail.com, peter@piie.net, dianders@chromium.org,
	linux-doc@vger.kernel.org, edubezval@gmail.com,
	linux-rockchip@lists.infradead.org,
	Laxman Dewangan <ldewangan@nvidia.com>,
	smbarber@google.com, Leo Yan <leo.yan@linaro.org>,
	cf@rock-chips.com, briannorris@google.com,
	Zhang Rui <rui.zhang@intel.com>, Andy Champ <andycham@amazon.com>
Subject: Re: [PATCH v3 1/5] thermal: Add support for hardware-tracked trip points
Date: Thu, 26 May 2016 08:34:34 +0800	[thread overview]
Message-ID: <5746449A.7070803@rock-chips.com> (raw)
In-Reply-To: <20160525164258.GA11807@e104805>


On 2016年05月26日 00:42, Javi Merino wrote:
> Hi Caesar,
>
> On Wed, May 25, 2016 at 11:47:45AM +0800, Caesar Wang wrote:
>> From: Sascha Hauer <s.hauer@pengutronix.de>
>>
>> This adds support for hardware-tracked trip points to the device tree
>> thermal sensor framework.
>>
>> The framework supports an arbitrary number of trip points. Whenever
>> the current temperature is updated, the trip points immediately
>> below and above the current temperature are found. A .set_trips
>> callback is then called with the temperatures. If there is no trip
>> point above or below the current temperature, the passed trip
>> temperature will be -INT_MAX or INT_MAX respectively. In this callback,
>> the driver should program the hardware such that it is notified
>> when either of these trip points are triggered. When a trip point
>> is triggered, the driver should call `thermal_zone_device_update'
>> for the respective thermal zone. This will cause the trip points
>> to be updated again.
>>
>> If .set_trips is not implemented, the framework behaves as before.
>>
>> This patch is based on an earlier version from Mikko Perttunen
>> <mikko.perttunen@kapsi.fi>
>>
>> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
>> Cc: Zhang Rui <rui.zhang@intel.com>
>> Cc: Eduardo Valentin <edubezval@gmail.com>
>> Cc: linux-pm@vger.kernel.org
>>
>> ---
>>
>> Changes in v3:
>> - as Javi comments on https://patchwork.kernel.org/patch/9001281/.
>> - add the lock for preventing the called from multi placce
>> - add the note for pre_low/high_trip.
>>
>> Changes in v2:
>> - update the sysfs-api.txt for set_trips.
>>
>>   Documentation/thermal/sysfs-api.txt |  7 +++++
>>   drivers/thermal/thermal_core.c      | 52 +++++++++++++++++++++++++++++++++++++
>>   include/linux/thermal.h             |  7 +++++
>>   3 files changed, 66 insertions(+)
>>
>> diff --git a/Documentation/thermal/sysfs-api.txt b/Documentation/thermal/sysfs-api.txt
>> index efc3f3d..75d8838 100644
>> --- a/Documentation/thermal/sysfs-api.txt
>> +++ b/Documentation/thermal/sysfs-api.txt
>> @@ -49,6 +49,9 @@ temperature) and throttle appropriate devices.
>>   	.bind: bind the thermal zone device with a thermal cooling device.
>>   	.unbind: unbind the thermal zone device with a thermal cooling device.
>>   	.get_temp: get the current temperature of the thermal zone.
>> +	.set_trips: set the trip points window. Whenever the current temperature
>> +		    is updated, the trip points immediately below and above the
>> +		    current temperature are found.
>>   	.get_mode: get the current mode (enabled/disabled) of the thermal zone.
>>   	    - "enabled" means the kernel thermal management is enabled.
>>   	    - "disabled" will prevent kernel thermal driver action upon trip points
>> @@ -95,6 +98,10 @@ temperature) and throttle appropriate devices.
>>   			get_temp:	a pointer to a function that reads the
>>   					sensor temperature. This is mandatory
>>   					callback provided by sensor driver.
>> +			set_trips:      a pointer to a function that sets a
>> +					temperature window. When this window is
>> +					left the driver must inform the thermal
>> +					core via thermal_zone_device_update.
>>   			get_trend: 	a pointer to a function that reads the
>>   					sensor temperature trend.
>>   			set_emul_temp:	a pointer to a function that sets
>> diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
>> index 5133cd1..e5bfbd3 100644
>> --- a/drivers/thermal/thermal_core.c
>> +++ b/drivers/thermal/thermal_core.c
>> @@ -520,6 +520,51 @@ exit:
>>   }
>>   EXPORT_SYMBOL_GPL(thermal_zone_get_temp);
>>   
>> +static void thermal_zone_set_trips(struct thermal_zone_device *tz)
>> +{
>> +	int low = -INT_MAX;
>> +	int high = INT_MAX;
>> +	int trip_temp, hysteresis;
>> +	int temp = tz->temperature;
>> +	int i, ret;
>> +
>> +	if (!tz->ops->set_trips)
>> +		return;
>> +
>> +	for (i = 0; i < tz->trips; i++) {
>> +		int trip_low;
>> +
>> +		tz->ops->get_trip_temp(tz, i, &trip_temp);
>> +		tz->ops->get_trip_hyst(tz, i, &hysteresis);
>> +
>> +		trip_low = trip_temp - hysteresis;
>> +
>> +		if (trip_low < temp && trip_low > low)
>> +			low = trip_low;
>> +
>> +		if (trip_temp > temp && trip_temp < high)
>> +			high = trip_temp;
>> +	}
>> +
>> +	/* No need to change trip points */
>> +	if (tz->prev_low_trip == low && tz->prev_high_trip == high)
>> +		return;
>> +
>> +	tz->prev_low_trip = low;
>> +	tz->prev_high_trip = high;
>> +
>> +	dev_dbg(&tz->device, "new temperature boundaries: %d < x < %d\n",
>> +			low, high);
>> +
>> +	/*
>> +	 * Set a temperature window. When this window is left the driver
>> +	 * must inform the thermal core via thermal_zone_device_update.
>> +	 */
>> +	ret = tz->ops->set_trips(tz, low, high);
>> +	if (ret)
>> +		dev_err(&tz->device, "Failed to set trips: %d\n", ret);
> In the v2 review
> (http://article.gmane.org/gmane.linux.documentation/38442) you agreed
> to add locking but you haven't done it.  Maybe you sent the wrong
> version?

My god!
Yep, I remember to change it. Somehow why ...

Thanks Javi for looking over it.

Hoping the next version is the final version.:-)

-Caesar

>
> Cheers,
> Javi
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip


-- 
caesar wang | software engineer | wxt@rock-chip.com

  reply	other threads:[~2016-05-26  0:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25  3:47 [PATCH v3 0/5] Thermal: Support for hardware-tracked trip points Caesar Wang
2016-05-25  3:47 ` Caesar Wang
2016-05-25  3:47 ` Caesar Wang
2016-05-25  3:47 ` [PATCH v3 1/5] thermal: Add support " Caesar Wang
2016-05-25  3:47   ` Caesar Wang
2016-05-25 16:42   ` Javi Merino
2016-05-26  0:34     ` Caesar Wang [this message]
2016-05-26  4:17       ` Caesar Wang
2016-05-25  3:47 ` [PATCH v3 2/5] thermal: of: implement .set_trips for device tree thermal zones Caesar Wang
2016-05-25 16:47   ` Javi Merino
2016-05-25  3:47 ` [PATCH v3 3/5] thermal: streamline get_trend callbacks Caesar Wang
2016-05-25  3:47 ` [PATCH v3 4/5] thermal: bang-bang governor: act on lower trip boundary Caesar Wang
2016-05-25  3:47   ` Caesar Wang
2016-05-25  3:47 ` [PATCH v3 5/5] thermal: rockchip: add the set_trips function Caesar Wang
2016-05-25  3:47   ` Caesar Wang

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=5746449A.7070803@rock-chips.com \
    --to=wxt@rock-chips.com \
    --cc=andycham@amazon.com \
    --cc=briannorris@google.com \
    --cc=cf@rock-chips.com \
    --cc=corbet@lwn.net \
    --cc=dianders@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=edubezval@gmail.com \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=javi.merino@arm.com \
    --cc=ldewangan@nvidia.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=peter@piie.net \
    --cc=rui.zhang@intel.com \
    --cc=s.hauer@pengutronix.de \
    --cc=smbarber@google.com \
    --cc=wni@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.