From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: ia64 acpi-cpufreq driver
Date: Mon, 23 Oct 2006 21:31:05 +0000 [thread overview]
Message-ID: <200610231531.05346.bjorn.helgaas@hp.com> (raw)
arch/ia64/kernel/cpufreq/acpi-cpufreq.c currently makes direct
calls to PAL_SET_PSTATE.
Section 8.4.4.1 (_PCT) of the 3.0 ACPI spec says:
OSPM performs processor performance transitions by writing
the performance state-specific control value to a Performance
Control Register (PERF_CTRL).
According to one of our architecture guys, this means we really
ought to have an OpRegion driver that encapsulates the PAL_SET_PSTATE
call.
I guess _PCT would return an acpi_generic_address in the FFixedHW
address space, and we would use acpi_hw_low_level_read() and
acpi_hw_low_level_write() to do the accesses (those functions
would need to be extended to support additional OpRegions, or
maybe I'm looking in the wrong place).
This sort of makes sense to me, because it would mean this part
of acpi-cpufreq wouldn't need to be ia64-specific. On x86, I
suppose _PCT would return a ACPI_ADR_SPACE_SYSTEM_IO address,
and acpi_processor_set_performance() could use acpi_hw_low_level_write()
instead of its own acpi_processor_write_port().
But I haven't seen anything resembling an ACPI FFH OpRegion
driver for Linux, or even a spec (e.g., a definition of what
the FFH address space contains) that would allow such a driver
to be written.
Any hints on what the future might hold in this area?
Bjorn
next reply other threads:[~2006-10-23 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 21:31 Bjorn Helgaas [this message]
2006-10-24 4:46 ` ia64 acpi-cpufreq driver Pallipadi, Venkatesh
2006-10-24 17:50 ` Bjorn Helgaas
2006-10-25 23:20 ` Bjorn Helgaas
2006-10-24 23:59 ` Pallipadi, Venkatesh
2006-10-25 3:47 ` Bjorn Helgaas
2006-10-26 4:36 ` Pallipadi, Venkatesh
2006-10-26 15:29 ` Bjorn Helgaas
2006-11-01 18:30 ` Pallipadi, Venkatesh
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=200610231531.05346.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=venkatesh.pallipadi@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