From: Mattia Dongili <malattia@linux.it>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
ego@in.ibm.com, Reuben Farrelly <reuben-linuxkernel@reub.net>,
Andrew Morton <akpm@osdl.org>,
davej@redhat.com, linux-kernel@vger.kernel.org,
CPUFreq Mailing List <cpufreq@lists.linux.org.uk>,
"Sadykov, Denis M" <denis.m.sadykov@intel.com>
Subject: [PATCH 2.6.19-rc5-mm2] cpufreq: set policy->curfreq on initialization
Date: Wed, 15 Nov 2006 20:05:17 +0100 [thread overview]
Message-ID: <20061115190517.GA2449@inferi.kami.home> (raw)
In-Reply-To: <20061115183610.GA4812@inferi.kami.home>
Check the correct variable and set policy->cur upon acpi-cpufreq
initialization to allow the userspace governor to be used as default.
Signed-off-by: Mattia Dongili <malattia@linux.it>
---
Reuben, could you also try if this patch fixes the BUG()?
Thanks
diff --git a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c b/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
index 18f4715..a630f94 100644
--- a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
+++ b/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
@@ -699,14 +699,14 @@ static int acpi_cpufreq_cpu_init(struct
if (result)
goto err_freqfree;
- switch (data->cpu_feature) {
+ switch (perf->control_register.space_id) {
case ACPI_ADR_SPACE_SYSTEM_IO:
/* Current speed is unknown and not detectable by IO port */
policy->cur = acpi_cpufreq_guess_freq(data, policy->cpu);
break;
case ACPI_ADR_SPACE_FIXED_HARDWARE:
acpi_cpufreq_driver.get = get_cur_freq_on_cpu;
- get_cur_freq_on_cpu(cpu);
+ policy->cur = get_cur_freq_on_cpu(cpu);
break;
default:
break;
next prev parent reply other threads:[~2006-11-15 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 18:06 2.6.19-rc5-mm2 Pallipadi, Venkatesh
2006-11-15 18:36 ` 2.6.19-rc5-mm2 Mattia Dongili
2006-11-15 19:05 ` Mattia Dongili [this message]
2006-11-17 13:56 ` [PATCH 2.6.19-rc5-mm2] cpufreq: set policy->curfreq on initialization Reuben Farrelly
2006-11-17 14:01 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=20061115190517.GA2449@inferi.kami.home \
--to=malattia@linux.it \
--cc=akpm@osdl.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=denis.m.sadykov@intel.com \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reuben-linuxkernel@reub.net \
--cc=venkatesh.pallipadi@intel.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
all inboxes | Powered by JetHome®