| Age | Commit message (Collapse) | Author |
|
- remove unnecessary usage of flags.performance
- remove double check of _PPC in acpi-cpufreq driver as it's handled in
drivers/acpi/processor.c already
- remove unneeded EXPORT_SYMBOL
- allocation of memory only for probed CPUs
- add unregistration function to the core
- fix OOPS when PST has core_frequency values of zero
- fix cpufreq_get() output
- fix /proc/acpi/processor/*/performance write support [deprecated]
|
|
updates the _PPC handling. It is handled as a CPUfreq
policy notifier which adjusts the maximum CPU speed
according to the current platform limit.
|
|
from Dominik Brodowski
The current algorithm used by Linux ACPI for passive thermal management has
two shortcomings:
- if increasing the CPU processing power as a thermal situation goes away,
throttling states are decreased later than performance states. This is
not wise -- it should be the opposite ordering of going "up".
- only if the ACPI CPUfreq driver is used, performance states are used.
A generalized approach would offer passive cooling even if the ACPI
P-States cpufreq driver cannot be used (faulty BIOS, FixedHW access, etc.)
|
|
from Jes Sorensen
|
|
clean up other resources too (Daniele Bellucci)
|
|
|
|
from Dmitry Torokhov.
I have the following problems with ACPI P-States driver:
- It crashes because it tries to switch CPU speed without registering cpufreq
driver first but acpi_processor_set_performance calls cpufreq_notify_transition.
- When testing for capable CPUs it skips all online ones so for my single CPU
notebook it can't activate at all.
- If a processor does not support throttling then it will say that "limit"
interface is not supported even after activating performance control.
The patch below should fix these issues. It also adds some info messages since
/proc/acpi/processor/*/performance interface is marked obsolete but i still
would like to see if P-states were recognized during boot.
|
|
Fixes unknown symbol copy_.. in some builds
|
|
into groveronline.com:/root/bk/linux-acpi
|
|
From Pavel Machek
|
|
|
|
us to think that some systems support C2 when they really don't.
|
|
(Thanks to Dominik Brodowski)
|
|
|
|
|
|
|
|
|
|
|
|
(Dominik Brodowski)
|
|
Allow for per-CPU initialization of CPUfreq. Therefore, it's not
necessary any longer to kmalloc the per-CPU policy struct. To use
this, cpufreq_driver->policy has to be set to NULL. Of course,
cpufreq_driver->init is needed then, which is the appropriate function
for CPU initialization. cpufreq_driver->exit is available for cleanup.
All existing drivers continue to work without any changes, just for
clarity ->init and ->exit are set to NULL, and the names accordingly.
|
|
|
|
|
|
|
|
|
|
This patch moves some basic per-CPU static information (minimum frequency,
maximum frequency and maximum transition latency) into a struct
cpufreq_cpuinfo. This offers a much cleaner struct cpufreq_driver and
struct cpufreq_policy.
|
|
|
|
|
|
This changes the return type of the verify and setpolicy functions from
void to int. While doing this, I've changed the values for minimum and
maximum supported frequency to be per CPU, as UltraSPARC needs this.
Additionally, small cleanups in various drivers.
|
|
|
|
- Clean up debug-only code
- Fix typo
- Correct walking of namespace, to prevent disappearance of processor and
thermal zone objects
- Fix button add calls to have the right handle (i.e. none)
- Prevent spurious cpufreq error
|
|
|
|
|
|
From Pavel Machek. Without these two lines,
the throttling limits are never reached, and a machine
will happily cook itself.
|
|
|
|
(Bjoern A. Zeeb)
|
|
what is needed by
multiple users.
|
|
|
|
|
|
Make people use the proper cli/sti replacements
|
|
Use acpi_os_free instead of kfree directly
Eliminate CONFIG_SMP ifdef and simplify errata.smp code
|
|
This patch removes the concept of "logical" CPU numbers, in
preparation for CPU hotplugging.
|
|
This adds an export so that processor.o and thermal.o can be compiled as
modules
|
|
1) Eliminate everywhere "if (0 == result)" is used, replace with
"if (!result)" and the like.
2) Move headers mysteriously included in the middle of the file to the top.
|
|
I don't know but it was dumb, so put them back.
|