diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2009-12-12 00:59:23 +0100 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-12-12 00:59:23 +0100 |
| commit | 2fe77b81c77eed92c4c0439f74c8148a295b4a86 (patch) | |
| tree | 8a5e33fc3804f29bbf5c95c2cd28ccbdaa4cf206 /Documentation/cpu-freq/user-guide.txt | |
| parent | Staging: batman: fix debug Kconfig option (diff) | |
| parent | [ACPI/CPUFREQ] Introduce bios_limit per cpu cpufreq sysfs interface (diff) | |
| download | linux-2fe77b81c77eed92c4c0439f74c8148a295b4a86.tar.xz linux-2fe77b81c77eed92c4c0439f74c8148a295b4a86.zip | |
Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/davej/cpufreq
* 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/davej/cpufreq:
[ACPI/CPUFREQ] Introduce bios_limit per cpu cpufreq sysfs interface
[CPUFREQ] make internal cpufreq_add_dev_* static
[CPUFREQ] use an enum for speedstep processor identification
[CPUFREQ] Document units for transition latency
[CPUFREQ] Use global sysfs cpufreq structure for conservative governor tunings
[CPUFREQ] Documentation: ABI: /sys/devices/system/cpu/cpu#/cpufreq/
[CPUFREQ] powernow-k6: set transition latency value so ondemand governor can be used
[CPUFREQ] cpumask: don't put a cpumask on the stack in x86...cpufreq/powernow-k8.c
Diffstat (limited to 'Documentation/cpu-freq/user-guide.txt')
| -rw-r--r-- | Documentation/cpu-freq/user-guide.txt | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/Documentation/cpu-freq/user-guide.txt b/Documentation/cpu-freq/user-guide.txt index 2a5b850847c0..04f6b32993e6 100644 --- a/Documentation/cpu-freq/user-guide.txt +++ b/Documentation/cpu-freq/user-guide.txt @@ -203,6 +203,17 @@ scaling_cur_freq : Current frequency of the CPU as determined by the frequency the kernel thinks the CPU runs at. +bios_limit : If the BIOS tells the OS to limit a CPU to + lower frequencies, the user can read out the + maximum available frequency from this file. + This typically can happen through (often not + intended) BIOS settings, restrictions + triggered through a service processor or other + BIOS/HW based implementations. + This does not cover thermal ACPI limitations + which can be detected through the generic + thermal driver. + If you have selected the "userspace" governor which allows you to set the CPU operating frequency to a specific value, you can read out the current frequency in |