public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot@poupinou.org>
To: len.brown@intel.com, acpi-devel@lists.sourceforge.net,
	cpufreq@www.linux.org.uk
Subject: Re: [ACPI] [PATCH] disable SMM access to SpeedStep using ACPI-FADT pstate_cnt
Date: Sun, 15 Feb 2004 15:54:07 +0100	[thread overview]
Message-ID: <20040215145407.GK13262@poupinou.org> (raw)
In-Reply-To: <20040215105712.GB6105@dominikbrodowski.de>

On Sun, Feb 15, 2004 at 11:57:12AM +0100, Dominik Brodowski wrote:
> Disable SMM access to SpeedStep
> 
> Often, the BIOS changes the CPU frequency if a notebook is (dis)connected
> from its AC adapter. This interferes with a) an user setting the CPU frequency
> and b) kernel timing code which needs to know loops_per_jiffy, cpu_khz etc.
> 
> So, ACPI 2.0 offers a method to disable such BIOS changes -- writing
> a value contained in the FADT (pstate_cnt) to the smi_cmd port. This patch
> utilizes this method by doing this write in processor.c.
> 
> However, most current notebooks only offer 1.0 ACPI tables, where the
> pstate_cnt entry is marked as "reserved". Whenever there is a _PCT entry
> in the DSDT, though [and this is only a 2.0 object!], we assume the
> "reserved" entry to be the pstate_cnt entry [if it isn't zero].

I would prefer to name it 'take_ownership' or something like that.  I think
this is the correct naming.

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

  reply	other threads:[~2004-02-15 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-15 10:57 [PATCH] disable SMM access to SpeedStep using ACPI-FADT pstate_cnt Dominik Brodowski
2004-02-15 14:54 ` Bruno Ducrot [this message]
2004-02-16  5:46   ` [ACPI] " Len Brown
2004-03-15 14:15     ` Dominik Brodowski
2004-02-16  5:29 ` Len Brown

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=20040215145407.GK13262@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=cpufreq@www.linux.org.uk \
    --cc=len.brown@intel.com \
    /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