From: Russell King <rmk@arm.linux.org.uk>
To: linux@brodo.de
Cc: cpufreq@www.linux.org.uk
Subject: Re: [BUG] 2.6.0: ARM won't build without CONFIG_CPU_FREQ_GOV_USERSPACE=y
Date: Fri, 26 Dec 2003 10:25:17 +0000 [thread overview]
Message-ID: <20031226102517.B8980@flint.arm.linux.org.uk> (raw)
In-Reply-To: <E1AZojC-00049i-00@mrelay00.kundenservices.net>; from linux@brodo.de on Fri, Dec 26, 2003 at 10:57:54AM +0100
On Fri, Dec 26, 2003 at 10:57:54AM +0100, linux@brodo.de wrote:
> IMO this should cause the default governor to be forced to "userspace",
> and the deprecated 2.4. API [including cpufreq_get()] to be activated as
> well.
Well, we can't deprecate "cpufreq_get()" because it is one of the
fundamental reasons for the CPUFREQ infrastructure was created. It
should be moved out of this file to somewhere it can live permanently
rather in a file marked as "deprecated".
> However, Kconfig thinks different: the default setting for
> CPU_FREQ_DEFAULT_GOV (see drivers/cpufreq/Kconfig) is PERFORMANCE, and
> this seems to take precedence over the "select". IMHO this is a Kconfig
> bug -- can you notify the maintainer of this issue, please?
Will do.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2003-12-26 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-26 9:57 [BUG] 2.6.0: ARM won't build without CONFIG_CPU_FREQ_GOV_USERSPACE=y linux
2003-12-26 10:25 ` Russell King [this message]
2003-12-28 21:51 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2003-12-25 16:00 Russell King
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=20031226102517.B8980@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=cpufreq@www.linux.org.uk \
--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.