From: Michal Rokos <michal@rokos.info>
To: cpufreq@www.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 PATCH] Missing default governors choices
Date: Thu, 26 Aug 2004 09:07:17 +0200 [thread overview]
Message-ID: <200408260907.17503.michal@rokos.info> (raw)
Hello,
aren't these 2 missing in "Default CPUFreq governor" menu?
Thank you.
Michal
PS: CC to me (I'm off the lists)
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/08/26 08:57:24+02:00 michal@rokos.info
# Add missing governors to "Default CPUFreq governor" menu.
#
# drivers/cpufreq/Kconfig
# 2004/08/26 08:57:13+02:00 michal@rokos.info +16 -0
# Add missing governors to "Default CPUFreq governor" menu.
#
diff -Nru a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig
--- a/drivers/cpufreq/Kconfig 2004-08-26 09:00:15 +02:00
+++ b/drivers/cpufreq/Kconfig 2004-08-26 09:00:15 +02:00
@@ -27,6 +27,14 @@
the frequency statically to the highest frequency supported by
the CPU.
+config CPU_FREQ_DEFAULT_GOV_POWERSAVE
+ bool "powersave"
+ select CPU_FREQ_GOV_POWERSAVE
+ help
+ Use the CPUFreq governor 'powersave' as default. This sets
+ the frequency statically to the lowest frequency supported by
+ the CPU.
+
config CPU_FREQ_DEFAULT_GOV_USERSPACE
bool "userspace"
select CPU_FREQ_GOV_USERSPACE
@@ -35,6 +43,14 @@
you to set the CPU frequency manually or when an userspace
programm shall be able to set the CPU dynamically without having
to enable the userspace governor manually.
+
+config CPU_FREQ_DEFAULT_GOV_ONDEMAND
+ bool "ondemand"
+ select CPU_FREQ_GOV_ONDEMAND
+ help
+ Use the CPUFreq governor 'ondemand' as default. This does
+ a periodic polling and changes frequency based on the CPU
+ utilization.
endchoice
next reply other threads:[~2004-08-26 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 7:07 Michal Rokos [this message]
2004-08-26 16:40 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=200408260907.17503.michal@rokos.info \
--to=michal@rokos.info \
--cc=cpufreq@www.linux.org.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®