From: Dominik Brodowski <linux-JhLEnvuH02M@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: Dominik Brodowski <devel-JhLEnvuH02M@public.gmane.org>,
Andrew Grover
<andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
ACPI mailing list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Thermal managment broken
Date: Wed, 18 Sep 2002 19:00:47 +0200 [thread overview]
Message-ID: <20020918190047.C921@brodo.de> (raw)
In-Reply-To: <20020918102555.GB18221-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>; from pavel-+ZI9xUNit7I@public.gmane.org on Wed, Sep 18, 2002 at 12:25:55PM +0200
Hi Pavel,
On Wed, Sep 18, 2002 at 12:25:55PM +0200, Pavel Machek wrote:
> > Additionally, it might be better to specify a "starting" and
> > "stopping" trip point - so that you don't have a fan going
> > on-off-on-off-on-off repeatedly. (IIRC someone complained about this a few
> > months ago on this list). But even without this "feature", I'd like to see
> > the user-specified trip points in the acpi patch.
>
> I believe this is orthogonal. You need to do two thresholds even
> without user help, so it needs to be solved some other way.
IIRC, that's something the DSDT has to provide - the trip points should
change (right in the DSDT) when the fan is turned on or off, respectively.
Many DSDTs don't do this, and this is an annoyance, but except some basic
"sanity checking" (for example, having a minimum fan-on period of x
seconds), such a policy interface should either provide such a two-threshold
policy itself (turn-off==user-value - 5°), or get direct user-input for it.
Dominik
-------------------------------------------------------
This SF.NET email is sponsored by: AMD - Your access to the experts
on Hammer Technology! Open Source & Linux Developers, register now
for the AMD Developer Symposium. Code: EX8664
http://www.developwithamd.com/developerlab
next prev parent reply other threads:[~2002-09-18 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 16:36 Thermal managment broken Pavel Machek
[not found] ` <20020916163600.GA11617-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2002-09-16 20:55 ` Dominik Brodowski
[not found] ` <20020916225518.B2247-JhLEnvuH02M@public.gmane.org>
2002-09-18 10:25 ` Pavel Machek
[not found] ` <20020918102555.GB18221-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2002-09-18 17:00 ` Dominik Brodowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-17 16:12 Herbert Nachtnebel
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=20020918190047.C921@brodo.de \
--to=linux-jhlenvuh02m@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=devel-JhLEnvuH02M@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@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