[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070521132711.GA7540@srcf.ucam.org>
Date: Mon, 21 May 2007 14:27:12 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Pavel Machek <pavel@....cz>
Cc: Len Brown <lenb@...nel.org>, trenn@...e.de,
Chuck Ebbert <cebbert@...hat.com>, len.brown@...el.com,
Maciej Rutecki <maciej.rutecki@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
torvalds@...ux-foundation.org
Subject: Re: 2.6.22-rc1-mm1 [cannot change thermal trip points]
On Mon, May 21, 2007 at 02:10:48PM +0200, Pavel Machek wrote:
> > nope, the OS can't reliably override the processor passive trip point.
> > That is what _SCP and cooling_mode are for.
>
> Yes, it is reliable if you turn on thermal polling.
As Len says, the system can force a reevaluation of the trip points at
any time which will wipe out the local settings. Either you ignore the
spec and the notifications (potentially risking misbehaving hardware) or
you end up in a perpetual race.
> > if you want to change the state of the fans,
> > then poke /proc/acpi/fan/ directly.
>
> Heh, you suggest this? It is even less functional than current
> solution -- which works okay as long as you keep thermal polling
> working.
If there are problems with the fan behaviour, why don't we fix them?
> > For folks with the reverse problem -- active cooling where the
> > fans kick in early than they'd like, they should just turn off
> > the fans via /proc/acpi/fan and not mess with the trip points at
> > all.
>
> No. Manually turning off fans is even worse hack.
It's significantly more correct.
--
Matthew Garrett | mjg59@...f.ucam.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists