From: Zhang Rui <rui.zhang@intel.com>
To: Wei Ni <wni@nvidia.com>
Cc: eduardo.valentin@ti.com, durgadoss.r@intel.com,
MLongnecker@nvidia.com, linux-pm@vger.kernel.org
Subject: Re: [PATCH v4 1/2] thermal: add available policies attribute
Date: Thu, 27 Feb 2014 15:06:10 +0800 [thread overview]
Message-ID: <1393484770.2637.18.camel@rzhang1-mobl4> (raw)
In-Reply-To: <1390211732-5853-2-git-send-email-wni@nvidia.com>
On Mon, 2014-01-20 at 17:55 +0800, Wei Ni wrote:
> The Linux thermal framework support to change thermal governor
> policy in userspace, but it can't show what available policies
> supported.
>
> This patch adds available_policies attribute to the thermal
> framework, it can list the thermal governors which can be
> used for a particular zone. This attribute is read only.
>
> Signed-off-by: Wei Ni <wni@nvidia.com>
applied.
thanks,
rui
> ---
> Documentation/thermal/sysfs-api.txt | 6 ++++++
> drivers/thermal/thermal_core.c | 28 ++++++++++++++++++++++++++++
> 2 files changed, 34 insertions(+)
>
> diff --git a/Documentation/thermal/sysfs-api.txt b/Documentation/thermal/sysfs-api.txt
> index 87519cb..8459d45 100644
> --- a/Documentation/thermal/sysfs-api.txt
> +++ b/Documentation/thermal/sysfs-api.txt
> @@ -172,6 +172,7 @@ Thermal zone device sys I/F, created once it's registered:
> |---temp: Current temperature
> |---mode: Working mode of the thermal zone
> |---policy: Thermal governor used for this zone
> + |---available_policies Available thermal governors for this zone
> |---trip_point_[0-*]_temp: Trip point temperature
> |---trip_point_[0-*]_type: Trip point type
> |---trip_point_[0-*]_hyst: Hysteresis value for this trip point
> @@ -238,6 +239,10 @@ policy
> One of the various thermal governors used for a particular zone.
> RW, Required
>
> +available_policies
> + Available thermal governors which can be used for a particular zone.
> + RO, Required
> +
> trip_point_[0-*]_temp
> The temperature above which trip point will be fired.
> Unit: millidegree Celsius
> @@ -330,6 +335,7 @@ method, the sys I/F structure will be built like this:
> |---temp: 37000
> |---mode: enabled
> |---policy: step_wise
> + |---available_policies: step_wise fair_share
> |---trip_point_0_temp: 100000
> |---trip_point_0_type: critical
> |---trip_point_1_temp: 80000
> diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
> index 338a88b..a91684b 100644
> --- a/drivers/thermal/thermal_core.c
> +++ b/drivers/thermal/thermal_core.c
> @@ -761,6 +761,27 @@ policy_show(struct device *dev, struct device_attribute *devattr, char *buf)
> return sprintf(buf, "%s\n", tz->governor->name);
> }
>
> +static ssize_t
> +available_policies_show(struct device *dev, struct device_attribute *devattr,
> + char *buf)
> +{
> + struct thermal_governor *pos;
> + ssize_t count = 0;
> + ssize_t size = 0;
> +
> + mutex_lock(&thermal_governor_lock);
> +
> + list_for_each_entry(pos, &thermal_governor_list, governor_list) {
> + size = PAGE_SIZE - count;
> + count += scnprintf(buf + count, size, "%s ", pos->name);
> + }
> + count += scnprintf(buf + count, size, "\n");
> +
> + mutex_unlock(&thermal_governor_lock);
> +
> + return count;
> +}
> +
> #ifdef CONFIG_THERMAL_EMULATION
> static ssize_t
> emul_temp_store(struct device *dev, struct device_attribute *attr,
> @@ -794,6 +815,7 @@ static DEVICE_ATTR(temp, 0444, temp_show, NULL);
> static DEVICE_ATTR(mode, 0644, mode_show, mode_store);
> static DEVICE_ATTR(passive, S_IRUGO | S_IWUSR, passive_show, passive_store);
> static DEVICE_ATTR(policy, S_IRUGO | S_IWUSR, policy_show, policy_store);
> +static DEVICE_ATTR(available_policies, S_IRUGO, available_policies_show, NULL);
>
> /* sys I/F for cooling device */
> #define to_cooling_device(_dev) \
> @@ -1527,6 +1549,11 @@ struct thermal_zone_device *thermal_zone_device_register(const char *type,
> if (result)
> goto unregister;
>
> + /* Create available_policies attribute */
> + result = device_create_file(&tz->device, &dev_attr_available_policies);
> + if (result)
> + goto unregister;
> +
> /* Update 'this' zone's governor information */
> mutex_lock(&thermal_governor_lock);
>
> @@ -1622,6 +1649,7 @@ void thermal_zone_device_unregister(struct thermal_zone_device *tz)
> if (tz->ops->get_mode)
> device_remove_file(&tz->device, &dev_attr_mode);
> device_remove_file(&tz->device, &dev_attr_policy);
> + device_remove_file(&tz->device, &dev_attr_available_policies);
> remove_trip_attrs(tz);
> tz->governor = NULL;
>
next prev parent reply other threads:[~2014-02-27 7:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 9:55 [PATCH v4 0/2] Support to tune governor in run time Wei Ni
2014-01-20 9:55 ` [PATCH v4 1/2] thermal: add available policies attribute Wei Ni
2014-02-27 7:06 ` Zhang Rui [this message]
2014-01-20 9:55 ` [PATCH v4 2/2] thermal: add interface to support tune governor in run-time Wei Ni
2014-01-20 9:58 ` Wei Ni
2014-01-20 13:28 ` Eduardo Valentin
2014-02-27 7:10 ` Zhang Rui
2014-02-27 8:00 ` Wei Ni
2014-02-27 8:06 ` Zhang Rui
2014-02-27 8:21 ` Wei Ni
2014-01-20 18:58 ` [PATCH v4 0/2] Support to tune governor in run time Matthew Longnecker
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=1393484770.2637.18.camel@rzhang1-mobl4 \
--to=rui.zhang@intel.com \
--cc=MLongnecker@nvidia.com \
--cc=durgadoss.r@intel.com \
--cc=eduardo.valentin@ti.com \
--cc=linux-pm@vger.kernel.org \
--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 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).