From: george anzinger <george@mvista.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.5.32] CPU frequency and voltage scaling (0/4)
Date: Thu, 29 Aug 2002 14:22:51 -0700 [thread overview]
Message-ID: <3D6E90AB.FBA3BDE6@mvista.com> (raw)
In-Reply-To: aklq8b$220$1@penguin.transmeta.com
Linus Torvalds wrote:
>
> In article <1030618420.7290.112.camel@irongate.swansea.linux.org.uk>,
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >> { min-Hz, max-Hz, policy }
> >>
> >
> >For a few of the processors "event-hz" or similar would be nice. The
> >Geode supports hardware assisted bursting to full processor speed when
> >doing SMM, I/O and IRQ handling.
>
> Hmm.. I would assume that you'd just use the high frequency for that?
> So, for example, assuming you have a 600/300 Geode, when you do
>
> { 0, ~0UL, "power-save" }
>
> that would tell the Geode driver to run at 300MHz normally
> ("power-save"), and at 600Mhz when doing critical events.
>
> In contrast, a
>
> { 0, ~0UL, "performance" }
>
> mode would mean that it always runs at 600MHz (modulo heat throttling,
> of course).
>
> And a
>
> { 300, 300, "power-save" }
How about { 50, 50, "power-save" } where the number refers
to percent of full?
I.e. same meaning IFF full is 600, but suppose it is 800.
>
> means that you want the chip to always run at 300MHz, even when handling
> critical events.
>
> I don't know the exact details of what kinds of frequencies the Geode
> supports, but it sounds to me like you don't really need another
> frequency value..
>
> Linus
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2002-08-29 21:18 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
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 [this message]
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=3D6E90AB.FBA3BDE6@mvista.com \
--to=george@mvista.com \
--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