summaryrefslogtreecommitdiffstats
path: root/arch/i386/kernel/cpu/cpufreq/powernow-k8.h (follow)
Commit message (Collapse)AuthorAgeFilesLines
* i386: move kernel/cpu/cpufreqThomas Gleixner2007-10-111-232/+0
| | | | | Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Ingo Molnar <mingo@elte.hu>
* [CPUFREQ] Correct revision mask for powernow-k8Dave Jones2007-05-151-1/+1
| | | | | | | | Mark Langsdorf points out that the correct define for this revision bump is 0x80000. Also to save us having to keep renaming the #define, give it a more meaningful name. Signed-off-by: Dave Jones <davej@redhat.com>
* [CPUFREQ] Support rev H AMD64s in powernow-k8Dave Jones2007-05-131-2/+2
| | | | | Reported-by: Calvin Dodge <caldodge@gmail.com> Signed-off-by: Dave Jones <davej@redhat.com>
* [CPUFREQ] do not declare undefined functionsDavid Rientjes2007-04-301-0/+2
| | | | | | | | fill_powernow_table_pstate() and fill_powernow_table_fidvid() are only defined and used for X86_POWERNOW_K8_ACPI. Signed-off-by: David Rientjes <rientjes@google.com> Signed-off-by: Dave Jones <davej@redhat.com>
* [CPUFREQ] correct powernow-k8 fid/vid masks for extended partsLangsdorf, Mark2006-06-201-1/+3
| | | | | | | | | The fid/vid masks for parts using the extended parts are slightly incorrect and can result in incorrect fid/vid codes being applied. No instances of this problem have been reported in the field but it could be a problem with future parts. Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com> Signed-off-by: Dave Jones <davej@redhat.com>
* [CPUFREQ] Prepare powernow-k8 for future CPUs.Dave Jones2006-06-051-3/+37
| | | | | | | | | Forthcoming AMD products will use a different algorithm for transitioning pstates than the current generation Opteron products do. The attached patch allows the powernow-k8 driver to work with those products. Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com> Signed-off-by: Dave Jones <davej@redhat.com>
* [CPUFREQ] powernow: remove private for_each_cpu_mask()Andrew Morton2006-03-271-4/+0
| | | | | | | It is unneeded and wrong. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Dave Jones <davej@redhat.com>
* [CPUFREQ] Lots of whitespace & CodingStyle cleanup.Dave Jones2006-02-281-3/+3
| | | | Signed-off-by: Dave Jones <davej@redhat.com>
* [PATCH] Support 100 MHz frequency transitionsLangsdorf, Mark2005-11-291-4/+5
| | | | | | | | | | | | Future versions of the Opteron processor may support frequency transitions of 100 MHz, instead of the=20 current 200 MHz. This patch enables the powernow-k8 driver to transition to an odd FID code, indicating a multiple of 100 MHz frequency. Signed-off-by: Jacob Shin <jacob.shin@amd.com> Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com> Signed-off-by: Dave Jones <davej@redhat.com>
* Fix up powernow-k8 compile. (Missing definitions).Dave Jones2005-07-291-0/+2
| | | | | From: Mark Langsdorf <mark.langsdorf@amd.com> Signed-off-by: Dave Jones <davej@redhat.com>
* Opteron revision F will support higher frequencies thanDave Jones2005-07-281-13/+17
| | | | | | | | | | | | | | can be encoded in the current driver's 4 bit frequency field. This patch updates the driver to support Rev F including 6 bit FIDs and processor ID updates. This should apply cleanly whether or not the dual-core bugfix I sent out last week is applied. I'd prefer that both get applied, of course. Signed-off-by: David Keck <david.keck@amd.com> Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com> Signed-off-by: Dave Jones <davej@redhat.com>
* [CPUFREQ] dual-core powernow-k8Dave Jones2005-06-011-0/+15
| | | | | | | | | | | | | With the release of the dual-core AMD Opterons last week, it's high time that cpufreq supported them. The attached patch applies cleanly to 2.6.12-rc3 and updates powernow-k8 to support the latest Athlon 64 and Opteron processors. Update the driver to version 1.40.0 and provide support for dual-core processors. Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com> Signed-off-by: Dave Jones <davej@redhat.com>
* Linux-2.6.12-rc2v2.6.12-rc2Linus Torvalds2005-04-171-0/+176
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!