From: sjhill@realitydiluted.com
To: linux-kernel@vger.kernel.org
Cc: sjhill@realitydiluted.com
Subject: [PATCH] Speedstep for 2.0GHz Centrino (Dothan Core)...
Date: Sat, 11 Dec 2004 10:38:24 -0600 [thread overview]
Message-ID: <E1CdAGG-0000ZL-9T@real.realitydiluted.com> (raw)
This patch adds the 2GHz Dothan based core to the speedstep infrastructure
for Linux. I have been able to utilize 600MHz and 2GHz with no troubles,
but the intermediate V/f pairs do not work. When I attempt to change the
frequency in /proc, the command hangs. I then have to kill the process
from a different terminal. If anyone else is utilizing this core and has
different experiences, I would be interested. Also, I am not on LKML, so
kindly CC: on replies. Cheers.
-Steve
--- linux-2.6.9/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c.orig 2004-12-01 08:27:00.000000000 -0600
+++ linux-2.6.9/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c 2004-12-01 09:13:33.000000000 -0600
@@ -197,7 +197,25 @@
OP(1700, 1484),
{ .frequency = CPUFREQ_TABLE_END }
};
-#undef OP
+
+/*
+ * These voltage tables were derived from the Intel Pentium M on 90-nm
+ * Process with 2-MB L2 Cache, document 30218904.pdf, Table 5, VID#C.
+ */
+
+/* Intel Pentium M processor 2.00GHz (Dothan) */
+static struct cpufreq_frequency_table dothan_2000[] =
+{
+ OP( 600, 988),
+ OP( 800, 1036),
+ OP(1000, 1084),
+ OP(1200, 1132),
+ OP(1400, 1180),
+ OP(1600, 1228),
+ OP(1800, 1276),
+ OP(2000, 1308),
+ { .frequency = CPUFREQ_TABLE_END }
+};
#define _BANIAS(cpuid, max, name) \
{ .cpu_id = cpuid, \
@@ -207,6 +225,13 @@
}
#define BANIAS(max) _BANIAS(&cpu_ids[CPU_BANIAS], max, #max)
+#define _DOTHAN(cpuid, max_khz, max_ghz) \
+{ .cpu_id = cpuid, \
+ .model_name = "Intel(R) Pentium(R) M processor" max_ghz "GHz", \
+ .max_freq = (max_khz)*1000, \
+ .op_points = dothan_##max_khz, \
+}
+
/* CPU models, their operating frequency range, and freq/voltage
operating points */
static struct cpu_model models[] =
@@ -224,12 +249,15 @@
/* NULL model_name is a wildcard */
{ &cpu_ids[CPU_DOTHAN_A1], NULL, 0, NULL },
{ &cpu_ids[CPU_DOTHAN_A2], NULL, 0, NULL },
- { &cpu_ids[CPU_DOTHAN_B0], NULL, 0, NULL },
+
+ _DOTHAN(&cpu_ids[CPU_DOTHAN_B0], 2000, " 2.00"),
{ NULL, }
};
#undef _BANIAS
#undef BANIAS
+#undef _DOTHAN
+#undef OP
static int centrino_cpu_init_table(struct cpufreq_policy *policy)
{
reply other threads:[~2004-12-11 16:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1CdAGG-0000ZL-9T@real.realitydiluted.com \
--to=sjhill@realitydiluted.com \
--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®