An error occurred fetching the project authors.
- 15 Jul, 2003 2 commits
-
-
Dave Jones authored
These are totally pointless as most of the development is now done either in bitkeeper, or patches directly to mainline.
-
Dave Jones authored
From Dominik Instead of trying to guess what the user intended, fail if the user requests a setting which is not supported by the longrun driver.
-
- 05 Jun, 2003 1 commit
-
-
Dave Jones authored
-
- 17 Mar, 2003 1 commit
-
-
Dave Jones authored
-
- 08 Mar, 2003 1 commit
-
-
Dave Jones authored
This patch takes use of the now-working cpufreq_interface.kset and cpufreq_policy.kobj to use reference counting within the cpufreq core wherever this is more appropriate than the previous approach -- using one semaphore. Additionally, the callbacks to the driver modules are protected now.
-
- 01 Mar, 2003 1 commit
-
-
Dominik Brodowski authored
Update x86 drivers so that they can live with the new cpufreq governor "userspace". sparc64 doesn't need any change, and I'll send the corresponding patch for ARM to Russell King.
-
- 24 Feb, 2003 1 commit
-
-
Michael Hayes authored
This fixes: neccessary -> necessary unneccessary -> unnecessary Fixes 46 occurrences in all.
-
- 23 Feb, 2003 1 commit
-
-
Dominik Brodowski authored
- switch the Intel x86 speedstep/Pentium 4/Xeon drivers and the Transmeta Crusoe Longrun driver to use the advanced cpufreq_driver registration process - cleanups - spelling fixes (Petri Koistinen) - thanks!
-
- 12 Feb, 2003 2 commits
-
-
Dave Jones authored
-
Dave Jones authored
From Dominik Brodowski
-
- 13 Jan, 2003 1 commit
-
-
Dominik Brodowski authored
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.
-
- 15 Dec, 2002 1 commit
-
-
Dominik Brodowski authored
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.
-
- 22 Nov, 2002 1 commit
-
-
Dominik Brodowski authored
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.
-
- 04 Nov, 2002 1 commit
-
-
Dominik Brodowski authored
Both the /proc/sys/cpu/ and /proc/cpufreq interface can safely be enabled in the same kernel. This simplifies the transition to the newer interface. Only minor updates are needed in order to allow this to be done.
-
- 29 Sep, 2002 2 commits
-
-
Dominik Brodowski authored
- incorrect pointer calculation spotted by Gerald Britton - speedstep.c cleanup (Gerald Britton)
-
Dominik Brodowski authored
CPUFreq i386 drivers for 2.5.39: arch/i386/config.in Necessary config options arch/i386/kernel/cpu/Makefile allow for compilation of the CPUFreq subdirectory arch/i386/kernel/cpu/cpufreq/Makefile Makefile for CPUFreq drivers arch/i386/kernel/cpu/cpufreq/elanfreq.c CPUFreq driver for AMD Elan processors arch/i386/kernel/cpu/cpufreq/longhaul.c CPUFreq driver for VIA Longhaul processors arch/i386/kernel/cpu/cpufreq/longrun.c CPUFreq driver for Transmeta Crusoe processors arch/i386/kernel/cpu/cpufreq/p4-clockmod.c CPUFreq driver for Pentium 4 Xeon processors (using clock modulation) arch/i386/kernel/cpu/cpufreq/powernow-k6.c CPUFreq driver for mobile AMD K6-2+ and mobile AMD K6-3+ processors arch/i386/kernel/cpu/cpufreq/speedstep.c CPUFreq drivers for ICH2-M and ICH3-M chipsets and Intel Pentium 3-M and 4-M processors.
-