From: Sebastian Henschel <acpi-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: Thomas Renninger <mail-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [ACPI-sppt] active cooling, amount of trippoints, specification
Date: Wed, 11 Feb 2004 13:43:54 +0100 [thread overview]
Message-ID: <20040211124354.GB8581@fuchi> (raw)
In-Reply-To: <402A18DC.701-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]
hello thomas..
* Thomas Renninger <mail-smMupaH/RwJM7kwft8N7nw@public.gmane.org> [2004-02-11 13:34 +0100]:
>
> please correct me if I am wrong:
>
> At least the /proc interface only allows to modify two active cooling
> trippoints.
> e.g. echo critical:hot:passive:active1:active2
> >/proc/acpi/thermal_zone/*/trip_points
>
> The ACPI specification (2.0b) specifies up to ten different trippoints
> for active cooling(p.284).
>
> Is everything inside the kernel designed for only supporting two active
> cooling trippoints?
> Is it going to change(specially the /proc/.../trip_points interface) to
> control the amount of active cooling
> devices as mentioned in the specs?
coincidently, i had a brief discussion with pavel machek about this last
week and he told me:
---------------
> did you also take into account that there may be more than 2 active
> levels? according to the spec, there should be 10 possible levels
> (12.3.1). is that implemented?
No, it is not implemented. I've seen machines with active[1], but not
ones with more active zones.
Feel free to do that... Code should really accept 4-13 parameters...
-----------------
bye,
sebastian
p.s.: diverted from acpi-support to acpi-devel intentionally.
--
::: .O.
::: ..O
::: OOO
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
parent reply other threads:[~2004-02-11 12:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <402A18DC.701-smMupaH/RwJM7kwft8N7nw@public.gmane.org>]
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=20040211124354.GB8581@fuchi \
--to=acpi-1rjuzeeg9oeb1svskn2v4q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mail-smMupaH/RwJM7kwft8N7nw@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