[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20090517180424.6836b46d.krzysztof.h1@wp.pl>
Date: Sun, 17 May 2009 18:04:24 +0200
From: Krzysztof Helt <krzysztof.h1@...pl>
To: cpufreq@...r.kernel.org
Cc: LKLM <linux-kernel@...r.kernel.org>
Subject: [PATCH] x86: Fix VIA C3 Longhaul v2 identification
From: Krzysztof Helt <krzysztof.h1@...pl>
An identification of the Longhaul versions (v1, v2 and v3) selects only
v1 or v3 version. There is a special case for late Samuel2 and early Ezra cores
which support the Longhaul v2 but the Longhaul v1 is selected. These cores
are described in the comment as supporting the Longhaul v2.
Select the Longhaul v2 for cores which support it.
Signed-off-by: Krzysztof Helt <krzysztof.h1@...pl>
---
I don't know if selecting the Longhaul v1 for these cores was a typo or done or
purpose. I cannot find any reference to this part of the code.
I have tested the change and it enables the Longhaul v2 on my Samuel2 core
but voltage change is not supported by my motherboard (PCChips something).
The voltage range is detected as a single value.
diff --git a/arch/x86/kernel/cpu/cpufreq/longhaul.c b/arch/x86/kernel/cpu/cpufreq/longhaul.c
index ce2ed3e..cabd2fa 100644
--- a/arch/x86/kernel/cpu/cpufreq/longhaul.c
+++ b/arch/x86/kernel/cpu/cpufreq/longhaul.c
@@ -813,7 +813,7 @@ static int __init longhaul_cpu_init(struct cpufreq_policy *policy)
memcpy(eblcr, samuel2_eblcr, sizeof(samuel2_eblcr));
break;
case 1 ... 15:
- longhaul_version = TYPE_LONGHAUL_V1;
+ longhaul_version = TYPE_LONGHAUL_V2;
if (c->x86_mask < 8) {
cpu_model = CPU_SAMUEL2;
cpuname = "C3 'Samuel 2' [C5B]";
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists