summaryrefslogtreecommitdiffstats
path: root/sys/i386/cpufreq
Commit message (Collapse)AuthorAgeFilesLines
* Add support for probing EST settings from ACPI. This should handle morenjl2005-03-211-77/+166
| | | | | | modern CPUs that have multiple VID#s that aren't detectable via public methods. We use the control value from acpi_perf as the id16 for setting a given frequency.
* Make a pass through all drivers checking specs for desired behavior onnjl2005-02-272-0/+15
| | | | | | | SMP systems. It appears all drivers except ichss should attach to each CPU and that settings should be performed on each CPU. Add comments about this. Also, add a guard for p4tcc's identify method being called more than once.
* Correct an off-by-one error in the number of settings est announces.njl2005-02-241-4/+3
| | | | The extraneous "0" state was not fatal but useless.
* Import a rewrite of p4tcc for the cpufreq(4) framework. This includesnjl2005-02-231-189/+197
| | | | | | a bugfix of clearing the On-Demand flag when going back to 100%. It has been tested and works on an IBM R32. Note original work done by Ted Unangst and sobomax@.
* Support disabling individual cpufreq drivers with hints, e.g.,njl2005-02-221-0/+3
| | | | hint.ichss.0.disabled="1"
* Add the Enhanced SpeedStep driver (EST). Currently, this driver only worksnjl2005-02-201-0/+785
| | | | | | | | | | on the previous generation of Pentium-M processors (Banias). Support for Dothan and later processors involves working with acpi_perf(4) to extract information about supported states. This driver should work on MP systems including HTT. It is experimental and may have a few bugs but has been tested to not crash at least. Thanks to Colin Percival for his initial work on this driver.
* Fix the problem with incorrect throttling level reported immediately aftersobomax2005-02-071-0/+11
| | | | | | | | | | | reboot. Safter the reboot the TCC is usually in the Automatic mode, in which reading current performance level is likely to produce bogus results make sure to switch it to the On-Demand mode and set to some known performance level. Unfortunately there is no reliable way to check that TCC is in the Automatic mode. Reading bit 4 of ACPI Thermal Monitor Control Register produces 0 regardless of the current mode. MFC after: 1 week
* Start all license/copyright notice comments with /*-, per traditionimp2005-01-051-1/+1
|
* o Fix whitespace bug introduced in the previous commit.sobomax2004-08-231-12/+4
| | | | | | | | Submitted by: ru o Simplify p4tcc_power_profile(). Submitted by: maxim
* o Extend boot output: print out mimimum/maximum performance value and numbersobomax2004-08-231-1/+19
| | | | | | | of performance steps available; o similarly to Enhanced SpeedStep driver, export list of all available steps via hw.p4tcc.cpuperf_levels sysctl.
* o Typo: Ternal -> Thermal.maxim2004-02-291-1/+1
|
* - Move performance-controlling sysctls into hw.p4tcc.* tree;sobomax2004-01-241-13/+18
| | | | | | | | | | Suggested by: nate - get rid of "magick" values in code and make sysctl's reflecting reality on processor versions which have one or another frequency "forbidden" due to errata. MFC after: 2 weeks
* Add new CPU_ENABLE_TCC option, from NOTES:sobomax2004-01-181-0/+244
CPU_ENABLE_TCC enables Thermal Control Circuitry (TCC) found in some Pentium(tm) 4 and (possibly) later CPUs. When enabled and detected, TCC allows to restrict power consumption by using machdep.cpuperf* sysctls. This operates independently of SpeedStep and is useful on systems where other mechanisms such as apm(4) or acpi(4) don't work. Given the fact that many, even modern, notebooks don't work properly with Intel ACPI, this is indeed very useful option for notebook owners. Obtained from: OpenBSD MFC after: 2 weeks
OpenPOWER on IntegriCloud