From: Eduardo Valentin <edubezval@gmail.com>
To: Srikar Srimath Tirumala <srikars@nvidia.com>
Cc: rui.zhang@intel.com, srinivas.pandruvada@intel.com,
linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
mlongnecker@nvidia.com
Subject: Re: [PATCH v3 4/4] thermal: update documentation for new device ops
Date: Mon, 2 May 2016 20:27:11 -0700 [thread overview]
Message-ID: <20160503032710.GB18752@localhost.localdomain> (raw)
In-Reply-To: <1459298497-29481-5-git-send-email-srikars@nvidia.com>
On Tue, Mar 29, 2016 at 05:41:37PM -0700, Srikar Srimath Tirumala wrote:
> Add documentation for two new thermal_zone_device_ops.
>
> Change-Id: Id1c5cc2ae4051a398dfe81c7ff0b27c1eab02579
> Signed-off-by: Srikar Srimath Tirumala <srikars@nvidia.com>
> ---
> Documentation/thermal/sysfs-api.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/thermal/sysfs-api.txt b/Documentation/thermal/sysfs-api.txt
> index ed419d6..13344167 100644
> --- a/Documentation/thermal/sysfs-api.txt
> +++ b/Documentation/thermal/sysfs-api.txt
> @@ -59,6 +59,11 @@ temperature) and throttle appropriate devices.
> will be fired.
> .set_emul_temp: set the emulation temperature which helps in debugging
> different threshold temperature points.
> + .get_trip_state: get the current state (TRIPPED or NOT_TRIPPED) of a
> + certain trip point.
> + .set_trip_state: set the state of a certain trip point.
> + .enb_temp_notify: check if temperature notifications are enabled for a
> + certain trip point.
I would prefer we merge this to the patch which is adding them.
> tzp: thermal zone platform parameters.
> passive_delay: number of milliseconds to wait between polls when
> performing passive cooling.
> --
> 2.1.4
>
prev parent reply other threads:[~2016-05-03 3:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 0:41 [PATCH v3 0/4] add sysfs_notify on some attributes Srikar Srimath Tirumala
2016-03-30 0:41 ` [PATCH v3 2/4] thermal: send notifications for tz temperature Srikar Srimath Tirumala
[not found] ` <1459298497-29481-3-git-send-email-srikars-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-30 16:43 ` Matt Longnecker
2016-03-30 16:53 ` Matt Longnecker
[not found] ` <1459298497-29481-1-git-send-email-srikars-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-30 0:41 ` [PATCH v3 1/4] thermal: send notifications for cdev state change Srikar Srimath Tirumala
[not found] ` <1459298497-29481-2-git-send-email-srikars-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-30 16:45 ` Matt Longnecker
2016-03-30 0:41 ` [PATCH v3 3/4] thermal: of: enable temperature notifications Srikar Srimath Tirumala
2016-03-30 16:54 ` Matt Longnecker
[not found] ` <1459298497-29481-4-git-send-email-srikars-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-03 3:26 ` Eduardo Valentin
2016-03-30 0:41 ` [PATCH v3 4/4] thermal: update documentation for new device ops Srikar Srimath Tirumala
[not found] ` <1459298497-29481-5-git-send-email-srikars-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-30 16:54 ` Matt Longnecker
2016-05-03 3:27 ` Eduardo Valentin [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=20160503032710.GB18752@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mlongnecker@nvidia.com \
--cc=rui.zhang@intel.com \
--cc=srikars@nvidia.com \
--cc=srinivas.pandruvada@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).