All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: davej@redhat.com, cpufreq@www.linux.org.uk
Subject: Re: [PATCH 2.6] powernow-k7 acpi support.
Date: Mon, 9 Feb 2004 16:05:19 +0100	[thread overview]
Message-ID: <20040209150519.GA6531@dominikbrodowski.de> (raw)
In-Reply-To: <20040209132659.GY13262@poupinou.org>


[-- Attachment #1.1: Type: text/plain, Size: 1814 bytes --]

> 1- Include the powernow_acpi_init() as the first call in
> powernow_decode_bios(), so that ACPI is used first, then if it failed,
> the legacy method is used,
> or
> 2- Include the powernow_acpi_init() at powernow_decode_bios() just
> before the 3 printk's stating to write that you should see
> http://www.codemonkey.org.uk/projects/cpufreq/...
> 
> I guess 2- is 'better', but I would like to get some thought, though.

Hm. That's difficult to decide, also for the speedstep-centrino case... I'd
like to hear some opinions from ACPI and AMD guys first before we decide...

> +	printk("1\n");
> +	if (acpi_processor_register_performance(&p, 0))
> +		return -EIO;
> +	printk("2\n");
> +
> +	r = &p.control_register;
> +	if (r->space_id != ACPI_ADR_SPACE_FIXED_HARDWARE) {

How about
	if (p.control_register.space_id != ACPI_ADR_SPACE_FIXED_HARDWARE) {
?

> +		retval = -ENODEV;
> +		goto out;
> +	}
> +	r = &p.status_register;
> +	if (r->space_id != ACPI_ADR_SPACE_FIXED_HARDWARE) {

same here...

> +	fsb = 100;	/* XXX fix me */

Any idea on how to determine the FSB?

> +	latency = 10000;	/* XXX don't trust bios writers.. */

heh...

> +	/*
> +	 * We don't need no more acpi.
> +	 * XXX is that true?
> +	 */

No, it's not true. If we use ACPI, we need to keep it registered until we
stop using it. Reasons:
- keep buggy drivers from interfering [e.g. other cpufreq drivers which 
  register with ACPI first and with cpufreq later, or avoid registering with
  cpufreq because of being proprietary...]
- honor _PPC limits
- allow for ACPI interface (additions):
  This includes the /proc/acpi/processor/./performance interface which
  people still tend to use, and additions to 
  /sys/devices/system/cpu/cpu0/cpufreq/ still to be written.


	Dominik

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq

  reply	other threads:[~2004-02-09 15:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-09 13:26 [PATCH 2.6] powernow-k7 acpi support Bruno Ducrot
2004-02-09 15:05 ` Dominik Brodowski [this message]
2004-02-09 15:20   ` Bruno Ducrot
2004-02-09 17:37     ` Bruno Ducrot
2004-02-09 17:50   ` Bruno Ducrot
2004-02-09 18:05     ` Dominik Brodowski
2004-02-09 18:29       ` Bruno Ducrot
2004-02-09 18:58       ` Bruno Ducrot
2004-02-10  9:03         ` Dominik Brodowski
2004-02-10 18:08           ` Dave Jones
2004-02-10 20:05             ` Bruno Ducrot

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=20040209150519.GA6531@dominikbrodowski.de \
    --to=linux@dominikbrodowski.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=ducrot@poupinou.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 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.