From: Matt Longnecker <mlongnecker-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Srikar Srimath Tirumala
<srikars-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
edubezval-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
srinivas.pandruvada-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3 2/4] thermal: send notifications for tz temperature
Date: Wed, 30 Mar 2016 09:43:01 -0700 [thread overview]
Message-ID: <56FC0215.1060802@nvidia.com> (raw)
In-Reply-To: <1459298497-29481-3-git-send-email-srikars-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 03/29/2016 05:41 PM, Srikar Srimath Tirumala wrote:
> * Update the 'temp' attr of a thermal_zone sysfs node, when the
> temperature goes above\below a trip point. Use sysfs_notify to send
> the notifications.
Rather than notifying temp, would it make sense to notify
trip_pointX_temp when temperature crosses the trip point going up and
trip_pointX_hyst when temperature crosses the trip point going down?
That would allow userspace to watch for only a subset of events by
polling/selecting on the relevant nodes.
>
> struct thermal_cooling_device_ops {
> @@ -348,6 +358,7 @@ struct thermal_zone_of_device_ops {
> * @temperature: temperature value in miliCelsius
> * @hysteresis: relative hysteresis in miliCelsius
> * @type: trip point type
> + * @state: trip point state
> */
>
> struct thermal_trip {
> @@ -355,6 +366,7 @@ struct thermal_trip {
> unsigned long int temperature;
> unsigned long int hysteresis;
> enum thermal_trip_type type;
> + enum thermal_trip_state state;
This looks vestigial. Remove it?
next prev parent reply other threads:[~2016-03-30 16:43 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 [this message]
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
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=56FC0215.1060802@nvidia.com \
--to=mlongnecker-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=edubezval-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=srikars-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=srinivas.pandruvada-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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).