linux.git/drivers/cpufreq, branch v3.0-rc2

cpufreq: make DB8500 cpufreq driver compile

2011-05-24T20:20:14+00:00

Concluding interface update and movement of the driver by making
the DB8500 cpufreq driver compile in the cpufreq subsystem.

Cc: Arnd Bergmann 
Acked-by: Dave Jones 
Signed-off-by: Linus Walleij

cpufreq: update DB8500 cpufreq driver

2011-05-24T20:20:05+00:00

This updates the ux500 cpufreq driver to the new interface from the
updated DB8500 PRCMU

Cc: Arnd Bergmann 
Acked-by: Dave Jones 
Signed-off-by: Linus Walleij

mach-ux500: move CPUfreq driver to cpufreq subsystem

2011-05-24T20:19:55+00:00

As part of the ARM arch subsystem migration, move the DB8500
cpufreq driver to drivers/cpufreq as discussed with Dave Jones. The
Makefile is not updated in order to avoid cross-subsystem conflicts
for this file in merges.

Cc: Arnd Bergmann 
Acked-by: Dave Jones 
Signed-off-by: Linus Walleij

Merge branch 'x86-cpu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip

2011-05-20T00:55:12+00:00

* 'x86-cpu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
  x86, cpu: Fix detection of Celeron Covington stepping A1 and B0
  Documentation, ABI: Update L3 cache index disable text
  x86, AMD, cacheinfo: Fix L3 cache index disable checks
  x86, AMD, cacheinfo: Fix fallout caused by max3 conversion
  x86, cpu: Change NOP selection for certain Intel CPUs
  x86, cpu: Clean up and unify the NOP selection infrastructure
  x86, percpu: Use ASM_NOP4 instead of hardcoding P6_NOP4
  x86, cpu: Move AMD Elan Kconfig under "Processor family"

Fix up trivial conflicts in alternative handling (commit dc326fca2b64
"x86, cpu: Clean up and unify the NOP selection infrastructure" removed
some hacky 5-byte instruction stuff, while commit d430d3d7e646 "jump
label: Introduce static_branch() interface" renamed HAVE_JUMP_LABEL to
CONFIG_JUMP_LABEL in the code that went away)

[CPUFREQ] Move x86 drivers to drivers/cpufreq/

2011-05-19T22:51:07+00:00

Signed-off-by: Dave Jones

[CPUFREQ] remove redundant sprintf from request_module call.

2011-05-04T15:50:58+00:00

Since format string handling is part of request_module, there is no
need to construct the module name. As such, drop the redundant sprintf
and heap usage.

Signed-off-by: Kees Cook 
Signed-off-by: Dave Jones

[CPUFREQ] cpufreq_stats.c: Fixed brace coding style issue

2011-05-04T15:50:58+00:00

Fixed brace coding style issue.

Signed-off-by: Karthigan Srinivasan 
Signed-off-by: Dave Jones

[CPUFREQ] Fix memory leak in cpufreq_stat

2011-05-04T15:50:57+00:00

When a CPU is taken offline in an SMP system, cpufreq_remove_dev()
nulls out the per-cpu policy before cpufreq_stats_free_table() can
make use of it.  cpufreq_stats_free_table() then skips the
call to sysfs_remove_group(), leaving about 100 bytes of sysfs-related
memory unclaimed each time a CPU-removal occurs. Break up
cpu_stats_free_table into sysfs and table portions, and
call the sysfs portion early.

Signed-off-by: Steven Finney 
Signed-off-by: Dave Jones 
Cc: stable@kernel.org

[CPUFREQ] use dynamic debug instead of custom infrastructure

2011-05-04T15:50:57+00:00

With dynamic debug having gained the capability to report debug messages
also during the boot process, it offers a far superior interface for
debug messages than the custom cpufreq infrastructure. As a first step,
remove the old cpufreq_debug_printk() function and replace it with a call
to the generic pr_debug() function.

How can dynamic debug be used on cpufreq? You need a kernel which has
CONFIG_DYNAMIC_DEBUG enabled.

To enabled debugging during runtime, mount debugfs and

$ echo -n 'module cpufreq +p' > /sys/kernel/debug/dynamic_debug/control

for debugging the complete "cpufreq" module. To achieve the same goal during
boot, append

	ddebug_query="module cpufreq +p"

as a boot parameter to the kernel of your choice.

For more detailled instructions, please see
Documentation/dynamic-debug-howto.txt

Signed-off-by: Dominik Brodowski 
Signed-off-by: Dave Jones

[CPUFREQ] CPU hotplug, re-create sysfs directory and symlinks

2011-05-04T15:50:57+00:00

When we discover CPUs that are affected by each other's
frequency/voltage transitions, the first CPU gets a sysfs directory
created, and rest of the siblings get symlinks. Currently, when we
hotplug off only the first CPU, all of the symlinks and the sysfs
directory gets removed. Even though rest of the siblings are still
online and functional, they are orphaned, and no longer governed by
cpufreq.

This patch, given the above scenario, creates a sysfs directory for
the first sibling and symlinks for the rest of the siblings.

Please note the recursive call, it was rather too ugly to roll it
out. And the removal of redundant NULL setting (it is already taken
care of near the top of the function).

Signed-off-by: Jacob Shin 
Acked-by: Mark Langsdorf 
Reviewed-by: Thomas Renninger 
Signed-off-by: Dave Jones 
Cc: stable@kernel.org