All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Longhaul - Only for "Powersaver"
Date: Thu, 13 Jul 2006 02:27:23 -0400	[thread overview]
Message-ID: <20060713062723.GB12807@redhat.com> (raw)
In-Reply-To: <44B5E0DD.9090109@interia.pl>

On Thu, Jul 13, 2006 at 07:57:49AM +0200, Rafał Bilski wrote:
 > Looks like ACPI C3 don't work with older VIA CPUs. Motherboard is 
 > ACPI C3 capable, but after C3 frequency is same as before.
 > So this patch below will make "longhaul" fail for older CPU's.
 > There is nothing what I can do to fix this. Looks like CPU with 
 > BCR2 MSR is changing frequency only on halt. Processor with 
 > Longhaul MSR is changing frequency on halt or ACPI C3.
 > Btw typo fixes.

Falling back to what we did in 2.6.17 for BCR2 systems may
get some of those working at least.  The whole notion of tying the
longhaul driver closely to acpi makes me nervous, as a lot of
those socket-370 boards have _dreadful_ ACPI BIOS implementations,
and in a large number of cases, will lack the necessary functionality
needed, as socket 370 Celerons were boring and had no fancy power
saving features to run in C3.

I really need to find time to dig out some of those old test systems, but that
won't happen now until after kernel summit/OLS/vacation.

 > @@ -627,7 +627,9 @@ static int __init longhaul_cpu_init(stru
 >  	switch (longhaul_version) {
 >  	case TYPE_LONGHAUL_V1:
 >  	case TYPE_LONGHAUL_V2:
 > -		printk ("Longhaul v%d supported.\n", longhaul_version);
 > +//		printk ("Longhaul v%d supported.\n", longhaul_version);
 > +		printk(KERN_ERR PFX "Processor don't support ACPI. Aborting.\n");

It's really a BIOS failing. The CPU cares nothing about how it's driven,
but if the DSDT lacks methods to do anything interesting, nothing happens.

 > @@ -691,8 +693,8 @@ static int __init longhaul_init(void)
 >  
 >  #ifdef CONFIG_SMP
 >  	if (num_online_cpus() > 1) {
 > -		return -ENODEV;
 >  		printk(KERN_ERR PFX "More than 1 CPU detected, longhaul disabled.\n");
 > +		return -ENODEV;

Applied this bit, but the other bit I need to think about some more.

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-07-13  6:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13  5:57 [PATCH] Longhaul - Only for "Powersaver" Rafał Bilski
2006-07-13  6:27 ` Dave Jones [this message]
2006-07-13  6:59   ` Rafał Bilski

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=20060713062723.GB12807@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=rafalbilski@interia.pl \
    /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.