cpufreq Archive on 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 - Protect user from himself
Date: Thu, 6 Jul 2006 15:50:30 -0400	[thread overview]
Message-ID: <20060706195030.GP13168@redhat.com> (raw)
In-Reply-To: <44A8AD7C.5030402@interia.pl>

On Mon, Jul 03, 2006 at 07:39:08AM +0200, Rafał Bilski wrote:
 > This patch depens on "Longhaul - Use hardware support".
 > 
 > Older CPU's require transition time >=1ms.
 > Print message for C7 user (this is based on real story).
 > 
 > Signed-off-by: Rafał Bilski <rafalbilski@interia.pl>
 > 
 > ---
 > 
 > --- linux-2.6.17-git20/arch/i386/kernel/cpu/cpufreq/longhaul.c.orig	2006-07-03 06:43:54.000000000 +0200
 > +++ linux-2.6.17-git20/arch/i386/kernel/cpu/cpufreq/longhaul.c	2006-07-03 07:33:38.000000000 +0200
 > @@ -633,6 +633,13 @@ static int __init longhaul_cpu_init(stru
 >  		break;
 >  	};
 >  
 > +#if (CONFIG_HZ > 250)
 > +	if (longhaul_version != TYPE_POWERSAVER) {
 > +		printk (KERN_INFO PFX "Timer frequency to high. Aborting\n");
 > +		return -EINVAL;
 > +	}
 > +#endif

This seems wrong.  We should adjust the timings based on HZ to sleep 
for less/more instead.

 > @@ -691,8 +698,9 @@ static int __init longhaul_init(void)
 >  	switch (c->x86_model) {
 >  	case 6 ... 9:
 >  		return cpufreq_register_driver(&longhaul_driver);
 > -	default:
 > -		printk (KERN_INFO PFX "Unknown VIA CPU. Contact davej@codemonkey.org.uk\n");
 > +	}
 > +	if (c->x86_model > 9) {
 > +		printk(KERN_INFO PFX "VIA C7 (or better) CPU. Use \"ACPI Processor P-States driver\".\n");

It can also use speedstep-centrino with some additional patches which I
need to dust off.

		Dave

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

      reply	other threads:[~2006-07-06 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03  5:39 [PATCH] Longhaul - Protect user from himself Rafał Bilski
2006-07-06 19:50 ` Dave Jones [this message]

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=20060706195030.GP13168@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox