linux.git/drivers/cpufreq, branch v2.6.26-rc2

[CPUFREQ] state info wrong after resume

2008-04-28T20:27:08+00:00

Sometimes old_index != stat->last_index, see cpufreq_update_policy, bios can
change cpu setting in resume.  In my test, after resume cpu is in lowest
speed, but the stat info shows cpu is in full speed.  This patch makes the
stat info correct after a resume.

Signed-off-by: Shaohua Li 
Signed-off-by: Andrew Morton 
Signed-off-by: Dave Jones

[CPUFREQ] allow use of the powersave governor as the default one

2008-04-28T20:27:08+00:00

Allow use of the powersave cpufreq governor as the default one for EMBEDDED
configs.

Signed-off-by: Alessandro Guido 
Signed-off-by: Andrew Morton 
Signed-off-by: Dave Jones

[CPUFREQ] expose cpufreq coordination requirements regardless of coordination mechanism

2008-04-28T20:27:08+00:00

Currently, affected_cpus shows which CPUs need to have their frequency
coordinated in software.  When hardware coordination is in use, the contents
of this file appear the same as when no coordination is required.  This can
lead to some confusion among user-space programs, for example, that do not
know that extra coordination is required to force a CPU core to a particular
speed to control power consumption.

To fix this, create a "related_cpus" attribute that always displays the
coordination map regardless of whatever coordination strategy the cpufreq
driver uses (sw or hw).  If the cpufreq driver does not provide a value, fall
back to policy->cpus.

Signed-off-by: Darrick J. Wong 
Signed-off-by: Andrew Morton 
Signed-off-by: Dave Jones

[CPUFREQ] fix show_trans_table

2008-04-28T19:05:44+00:00

Fix show_trans_table when it overflows PAGE_SIZE.

* Not all snprintf calls were protected against being passed a negative
length.
* When show_trans_table overflows, len might be > PAGE_SIZE. In that case,
returns PAGE_SIZE.

Signed-off-by: Cesar Eduardo Barros 
Signed-off-by: Dave Jones

[CPUFREQ] Warn when cpufreq_register_notifier called before pure initcalls

2008-04-28T19:05:44+00:00

If cpufreq_register_notifier is called before pure initcalls,
init_cpufreq_transition_notifier_list will overwrite whatever it did,
causing notifiers to be ignored.

Print some noise to the kernel log if that happens.

Signed-off-by: Cesar Eduardo Barros 
Signed-off-by: Dave Jones

[CPUFREQ] Refactor locking in cpufreq_add_dev

2008-04-28T19:05:42+00:00

Simplify this by moving the unlocking out of the error
paths into the exit path.

Signed-off-by: Dave Jones

[CPUFREQ] more CodingStyle

2008-04-28T19:05:42+00:00

void * p   ->  void *p
no space between function parameters
removed excess whitespace

Signed-off-by: Dave Jones

[CPUFREQ] CodingStyle

2008-04-28T19:05:41+00:00

return is not a function.

Signed-off-by: Dave Jones

[CPUFREQ] Slightly shorten the error paths of cpufreq_suspend/cpufreq_resume

2008-04-28T19:05:41+00:00

Signed-off-by: Dave Jones

[CPUFREQ] fix section mismatch warnings

2008-03-05T19:45:31+00:00

Fix the following warnings:
WARNING: vmlinux.o(.text+0xfe6711): Section mismatch in reference from the function cpufreq_unregister_driver() to the variable .cpuinit.data:cpufreq_cpu_notifier
WARNING: vmlinux.o(.text+0xfe68af): Section mismatch in reference from the function cpufreq_register_driver() to the variable .cpuinit.data:cpufreq_cpu_notifier
WARNING: vmlinux.o(.exit.text+0xc4fa): Section mismatch in reference from the function cpufreq_stats_exit() to the variable .cpuinit.data:cpufreq_stat_cpu_notifier

The warnings were casued by references to unregister_hotcpu_notifier()
from normal functions or exit functions.
This is flagged by modpost as a potential error because
it does not know that for the non HOTPLUG_CPU
scenario the unregister_hotcpu_notifier() is a nop.
Silence the warning by replacing the __initdata
annotation with a __refdata annotation.

Signed-off-by: Sam Ravnborg 
Signed-off-by: Dave Jones