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 - Fix hole
Date: Fri, 29 Dec 2006 15:57:29 -0500	[thread overview]
Message-ID: <20061229205729.GA27523@redhat.com> (raw)
In-Reply-To: <45957B5D.7070901@interia.pl>

On Fri, Dec 29, 2006 at 09:32:29PM +0100, Rafał Bilski wrote:
 > ACPI PM2 register was fallback for "Longhaul ver. 1" CPU's. 
 > My assumption that this register isn't present at 
 > "PowerSaver" motherboards is so far true, but current code 
 > will not work correctly in other case. There are three possible 
 > supports: ACPI C3, PM2 and northbridge. That was my assumption 
 > that ACPI C3 and northbridge is for PS and northbridge and PM2 
 > is for V1. In current code we can only check if it is ACPI 
 > support or not by port22_en. So remove port22_en and add 
 > longhaul_flags. If USE_ACPI_C3 and USE_NORTHBRIDGE are both 
 > clear then it means ACPI PM2 support. Also change order of 
 > support probe from ACPI C3, PM2, northbridge to ACPI C3, 
 > northbridge, ACPI PM2. Paranoid protection against port 0x22 
 > cast as ACPI PM2 register. Bit 1 clear in such case - lockup 
 > on AGP DMA. And obvious (now) fixup for do_powersaver. Use 
 > cx->address only for ACPI C3 ("PowerSaver" processor using 
 > PM2 support).

Much better description, thanks.
I renamed the subject "Fix up powersaver assumptions" which is a bit
more descriptive.
 
 > diff --git a/arch/i386/kernel/cpu/cpufreq/longhaul.c b/arch/i386/kernel/cpu/cpufreq/longhaul.c
 > --- a/arch/i386/kernel/cpu/cpufreq/longhaul.c
 > +++ b/arch/i386/kernel/cpu/cpufreq/longhaul.c
 > @@ -52,6 +52,10 @@
 > #define	CPU_EZRA_T	4
 > #define	CPU_NEHEMIAH	5
 > 
 > +/* Flags */
 > +#define USE_ACPI_C3		(1 << 1)
 > +#define USE_NORTHBRIDGE		(1 << 2)
 > +
 > static int cpu_model;
 > static unsigned int numscales=16;
 > static unsigned int fsb;

The diff got whitespace damaged this time, so I glued the
description above on the old diff, which applied
(after I fixed up the trailing whitespace addition which git hates).

Applied though finally :)

Thanks,

		Dave

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

  reply	other threads:[~2006-12-29 20:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-29 20:32 [PATCH] Longhaul - Fix hole Rafał Bilski
2006-12-29 20:57 ` Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-24 13:04 Rafał Bilski
2006-12-29  3:29 ` Dave Jones

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=20061229205729.GA27523@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