From: Pavel Machek <pavel@ucw.cz>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-acpi@vger.kernel.org, rjw@sisk.pl, lenb@kernel.org,
eduardo.valentin@ti.com
Subject: Re: [PATCH] ACPI thermal: do not always return THERMAL_TREND_RAISING for active trip points
Date: Sat, 27 Apr 2013 20:38:00 +0200 [thread overview]
Message-ID: <20130427183800.GA8929@amd.pavel.ucw.cz> (raw)
In-Reply-To: <1367065950.2128.11.camel@rzhang1-mobl4>
Hi!
> > Is that even right algoritm?
> >
> sorry the changelog is not clear enough here.
> I should say,
> "keep the fan on when the temperature is raising"
> "turn off the fan when the temperature is dropping"
>
> > Assume I'm running at very cold room, lets say -10C. Assume idle CPU
> > will hover around 30C with no fan, or hover around 10C with fan
> > running, trip point being 50C.
> >
> > You _could_ leave fan off until 50C, having silent, passively cooled
> > system.
> >
> > What it will do instead is annoyingly pulse fan at 10C.
> >
> First, fan will never spins on if the temperature never hits 50C.
>
> let's see how ACPI 3.0 fan (just have on and off state) is supposed to
> work after overheat.
> 1. temperature goes above 50C
> 2. Fan starts to spin.
> 3. a) if temperature goes higher (if possible), fan keeps on.
> b) if temperature drops, but still above 50C. the fan keeps on.
> c) if temperature drops below 50C, the last temperature is above 50C,
> thus the fan is turned off.
> d) if the temperature goes higher again, the fan will not spin on
> until the temperature is higher than the trip point (50C) again.
So the fan is spinning iff the temperature is over threshold, right?
> is this behavior what you want?
That's better, yes. Even better would be if it had some hysteresis:
turn the fan on at threshold temperature, but turn it off only if it
drops below temperature-5C, or if it is below threshold for 1 minute.
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2013-04-27 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 9:19 [PATCH] ACPI thermal: do not always return THERMAL_TREND_RAISING for active trip points Zhang Rui
2013-04-26 12:07 ` Rafael J. Wysocki
2013-04-27 10:23 ` Pavel Machek
2013-04-27 12:32 ` Zhang Rui
2013-04-27 18:38 ` Pavel Machek [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=20130427183800.GA8929@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=eduardo.valentin@ti.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=rui.zhang@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