From: Eduardo Valentin <edubezval@gmail.com>
To: "Chen, Yu C" <yu.c.chen@intel.com>
Cc: "Zhang, Rui" <rui.zhang@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 1/1] thermal: setup monitor only once after handling trips
Date: Mon, 30 Nov 2015 11:10:42 -0800 [thread overview]
Message-ID: <20151130191041.GB5900@localhost.localdomain> (raw)
In-Reply-To: <1448435910.15712.22.camel@localhost>
On Wed, Nov 25, 2015 at 07:16:08AM +0000, Chen, Yu C wrote:
> Hi,
> On Tue, 2015-11-24 at 20:07 -0800, Eduardo Valentin wrote:
> > Instead of changing the monitoring setup every time after
> > handling each trip, this patch simplifies the monitoring
> > setup by moving the setup call to a place where all
> > trips have been treated already.
> >
> > 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>
> > ---
> > drivers/thermal/thermal_core.c | 11 ++++++-----
> > 1 file changed, 6 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
> > index d9e525c..6debb54 100644
> > --- a/drivers/thermal/thermal_core.c
> > +++ b/drivers/thermal/thermal_core.c
> > @@ -457,11 +457,6 @@ static void handle_thermal_trip(struct thermal_zone_device *tz, int trip)
> > handle_critical_trips(tz, trip, type);
> > else
> > handle_non_critical_trips(tz, trip, type);
> > - /*
> > - * Alright, we handled this trip successfully.
> > - * So, start monitoring again.
> > - */
> > - monitor_thermal_zone(tz);
> > }
> >
> > /**
> > @@ -547,6 +542,12 @@ void thermal_zone_device_update(struct thermal_zone_device *tz)
> >
> > for (count = 0; count < tz->trips; count++)
> > handle_thermal_trip(tz, count);
> > +
> > + /*
> > + * Alright, we handled this trip successfully.
> s/these trips ?
Yeah, I can amend this.
> > + * So, start monitoring again.
> > + */
> > + monitor_thermal_zone(tz);
> > }
> > EXPORT_SYMBOL_GPL(thermal_zone_device_update);
> >
> BTW, thermal_notify_framework might need be affected?
Well, the original code does not call thermal_notify_framework. Calling
it would require a different patch. This one is just to simplify the
monitoring setup.
BR,
>
> thanks,
> Yu
prev parent reply other threads:[~2015-11-30 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 4:07 [PATCH 1/1] thermal: setup monitor only once after handling trips Eduardo Valentin
2015-11-25 7:16 ` Chen, Yu C
2015-11-30 19:10 ` 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=20151130191041.GB5900@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=yu.c.chen@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