From: Dominik Brodowski <devel@brodo.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
cpufreq@www.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.5.32] CPU frequency and voltage scaling (0/4)
Date: Thu, 29 Aug 2002 09:07:01 +0200 [thread overview]
Message-ID: <20020829090701.C1117@brodo.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0208281649540.27728-100000@home.transmeta.com>; from torvalds@transmeta.com on Wed, Aug 28, 2002 at 05:08:14PM -0700
On Wed, Aug 28, 2002 at 05:08:14PM -0700, Linus Torvalds wrote:
> I don't know how many policies would be needed (too many just adds
> complexity for no gain), but I _suspect_ that something like a
<snip>
> (maybe the "policy" thing actually makes a difference even for the
> fixed-frequency case: it can give hints about whether to allow C1-C3
> states when idle etc).
OK, I see the problems you mention wrt current cpufreq. But let's keep the
next version simple: and whether to allow C1-C3 is really nothing cpufreq
should take care of, as this is pure ACPI policy.
Dominik
next prev parent reply other threads:[~2002-08-29 7:07 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 11:46 [PATCH][2.5.32] CPU frequency and voltage scaling (0/4) Dominik Brodowski
2002-08-28 18:47 ` Linus Torvalds
2002-08-28 18:48 ` Cort Dougan
2002-08-28 19:25 ` Alan Cox
2002-08-28 19:32 ` Cort Dougan
2002-08-29 10:26 ` Zwane Mwaikambo
2002-08-28 19:41 ` Peter Riocreux
2002-08-28 19:58 ` Linus Torvalds
2002-08-29 9:51 ` Padraig Brady
2002-08-29 10:23 ` Zwane Mwaikambo
2002-08-28 19:21 ` Alan Cox
2002-08-28 19:49 ` Linus Torvalds
2002-08-28 20:25 ` Alan Cox
2002-08-28 20:29 ` Linus Torvalds
2002-08-28 23:26 ` Alan Cox
2002-08-28 23:49 ` Linus Torvalds
2002-08-30 0:39 ` jw schultz
2002-08-29 7:01 ` Dominik Brodowski
2002-08-28 20:39 ` Dominik Brodowski
2002-08-28 21:05 ` Linus Torvalds
2002-09-06 11:31 ` Pavel Machek
2002-08-28 20:27 ` Dominik Brodowski
2002-08-28 20:19 ` Dominik Brodowski
2002-08-28 20:43 ` Linus Torvalds
2002-08-28 20:53 ` Dominik Brodowski
2002-08-28 21:08 ` Linus Torvalds
2002-08-28 23:00 ` george anzinger
2002-08-28 23:30 ` Alan Cox
2002-08-29 0:08 ` Linus Torvalds
2002-08-29 7:07 ` Dominik Brodowski [this message]
2002-08-29 10:02 ` Padraig Brady
2002-08-29 10:53 ` Alan Cox
2002-08-29 13:38 ` Dave Jones
2002-08-29 18:47 ` Linus Torvalds
2002-08-29 19:24 ` Alan Cox
2002-08-29 21:22 ` george anzinger
2002-08-30 6:46 ` David Gibson
2002-08-30 7:54 ` Helge Hafting
2002-08-30 3:21 ` David Lang
-- strict thread matches above, loose matches on Subject: below --
2002-08-28 20:25 Grover, Andrew
2002-08-28 20:46 ` Linus Torvalds
2002-08-29 15:07 Pering, Trevor
2002-08-30 8:04 ` Helge Hafting
2002-08-30 11:53 ` Dave Jones
2002-08-30 12:36 ` Helge Hafting
2002-08-30 22:43 ` george anzinger
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=20020829090701.C1117@brodo.de \
--to=devel@brodo.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cpufreq@www.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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