From: Dominik Brodowski <devel-JhLEnvuH02M@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: Andrew Grover
<andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
ACPI mailing list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Thermal managment broken
Date: Mon, 16 Sep 2002 22:55:18 +0200 [thread overview]
Message-ID: <20020916225518.B2247@brodo.de> (raw)
In-Reply-To: <20020916163600.GA11617-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>; from pavel-+ZI9xUNit7I@public.gmane.org on Mon, Sep 16, 2002 at 06:36:01PM +0200
Hi Pavel, Andrew, list;
> First is strict bugfix, please take. Second is needed, please take it,
> too.
While I'd "vote" for the second patch "in general", there are two aspects
which should be mentioned first:
> + tz->trips.critical.temperature = CELSIUS_TO_KELVIN(critical);
> + tz->trips.hot.temperature = CELSIUS_TO_KELVIN(hot);
> + tz->trips.passive.temperature = CELSIUS_TO_KELVIN(passive);
> + tz->trips.active[0].temperature = CELSIUS_TO_KELVIN(active0);
> + tz->trips.active[1].temperature = CELSIUS_TO_KELVIN(active1);
You explicitely want to support _two_ active trip points here. While this
seems to be the amount of active trip points seen on most systems, I'd
prefer you'd do a more flexible interface [zero to ACPI_THERMAL_MAX_ACTIVE
would be best].
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.
Dominik
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-09-16 20:55 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 [this message]
[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
-- 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=20020916225518.B2247@brodo.de \
--to=devel-jhlenvuh02m@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.