From: Pavel Machek <pavel@ucw.cz>
To: Dominik Brodowski <linux@brodo.de>
Cc: danielk@mrl.nyu.edu, cpufreq@www.linux.org.uk,
linux-kernel@vger.kernel.org,
Mattia Dongili <dongili@supereva.it>
Subject: Re: [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI P-state driver
Date: Thu, 23 Oct 2003 16:32:43 +0200 [thread overview]
Message-ID: <20031023143242.GH643@openzaurus.ucw.cz> (raw)
In-Reply-To: <20031021203215.GE26971@brodo.de>
Hi!
> Yes indeed. She wants to set a cpufreq policy which suits of her needs:
> it consists of a
> - minimum frequency => not too low [she's plugged in]
I just hope minimum frequency is not going to be
honoured in case of overheat.
Issue is what happens if user specifies range containing no
valid frequency. Kernel currently uses next _higher_
frequency, but going for next lower one seems to be
important (burning cpus, exploding batteries, ...)
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Dominik Brodowski <linux@brodo.de>
Cc: danielk@mrl.nyu.edu, Mattia Dongili <dongili@supereva.it>,
linux-kernel@vger.kernel.org, cpufreq@www.linux.org.uk
Subject: Re: [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI P-state driver
Date: Thu, 23 Oct 2003 16:32:43 +0200 [thread overview]
Message-ID: <20031023143242.GH643@openzaurus.ucw.cz> (raw)
In-Reply-To: <20031021203215.GE26971@brodo.de>
Hi!
> Yes indeed. She wants to set a cpufreq policy which suits of her needs:
> it consists of a
> - minimum frequency => not too low [she's plugged in]
I just hope minimum frequency is not going to be
honoured in case of overheat.
Issue is what happens if user specifies range containing no
valid frequency. Kernel currently uses next _higher_
frequency, but going for next lower one seems to be
important (burning cpus, exploding batteries, ...)
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2003-10-23 14:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 2:56 [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI P-state driver Pallipadi, Venkatesh
2003-10-21 2:56 ` Pallipadi, Venkatesh
2003-10-21 8:38 ` Arjan van de Ven
2003-10-21 8:38 ` Arjan van de Ven
2003-10-21 9:59 ` Mattia Dongili
2003-10-21 9:59 ` Mattia Dongili
2003-10-21 10:17 ` Wichert Akkerman
2003-10-21 10:52 ` Mattia Dongili
2003-10-21 12:59 ` Wichert Akkerman
2003-10-21 15:36 ` Daniel Thor Kristjansson
2003-10-21 20:32 ` Dominik Brodowski
2003-10-21 20:32 ` Dominik Brodowski
2003-10-22 15:48 ` Daniel Thor Kristjansson
2003-10-22 15:48 ` Daniel Thor Kristjansson
2003-10-23 14:32 ` Pavel Machek [this message]
2003-10-23 14:32 ` Pavel Machek
2003-10-24 18:22 ` Dominik Brodowski
2003-10-24 18:22 ` Dominik Brodowski
2003-10-21 19:23 ` Carl Thompson
2003-10-21 20:37 ` Dominik Brodowski
2003-10-21 20:37 ` Dominik Brodowski
2003-10-21 20:44 ` Dominik Brodowski
2003-10-21 20:59 ` Dominik Brodowski
2003-10-23 14:17 ` Pavel Machek
2003-10-23 14:17 ` Pavel Machek
2003-10-23 20:47 ` Moore, Robert
2003-10-23 20:47 ` Moore, Robert
2003-10-23 21:50 ` Nakajima, Jun
2003-10-23 21:50 ` Nakajima, Jun
2003-10-24 18:38 ` Dominik Brodowski
2003-10-24 18:38 ` Dominik Brodowski
2003-10-24 11:27 ` Ducrot Bruno
2003-10-24 11:27 ` Ducrot Bruno
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 5:50 Pallipadi, Venkatesh
2003-10-24 18:52 Pallipadi, Venkatesh
2003-10-24 18:52 ` Pallipadi, Venkatesh
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=20031023143242.GH643@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=cpufreq@www.linux.org.uk \
--cc=danielk@mrl.nyu.edu \
--cc=dongili@supereva.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
/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.