28 Apr, 2013
1 commit
-
* pm-cpufreq: (57 commits)
cpufreq: MAINTAINERS: Add co-maintainer
cpufreq: pxa2xx: initialize variables
ARM: S5pv210: compiling issue, ARM_S5PV210_CPUFREQ needs CONFIG_CPU_FREQ_TABLE=y
cpufreq: cpu0: Put cpu parent node after using it
cpufreq: ARM big LITTLE: Adapt to latest cpufreq updates
cpufreq: ARM big LITTLE: put DT nodes after using them
cpufreq: Don't call __cpufreq_governor() for drivers without target()
cpufreq: exynos5440: Protect OPP search calls with RCU lock
cpufreq: dbx500: Round to closest available freq
cpufreq: Call __cpufreq_governor() with correct policy->cpus mask
cpufreq / intel_pstate: Optimize intel_pstate_set_policy
cpufreq: OMAP: instantiate omap-cpufreq as a platform_driver
arm: exynos: Enable OPP library support for exynos5440
cpufreq: exynos: Remove error return even if no soc is found
cpufreq: exynos: Add cpufreq driver for exynos5440
cpufreq: AMD "frequency sensitivity feedback" powersave bias for ondemand governor
cpufreq: ondemand: allow custom powersave_bias_target handler to be registered
cpufreq: convert cpufreq_driver to using RCU
cpufreq: powerpc/platforms/cell: move cpufreq driver to drivers/cpufreq
cpufreq: sparc: move cpufreq driver to drivers/cpufreq
...Conflicts:
MAINTAINERS (with commit a8e39c3 from pm-cpuidle)
drivers/cpufreq/cpufreq_governor.h (with commit beb0ff3)
10 Apr, 2013
1 commit
-
This function is called quite often from other subsystems.
Removed unused call to intel_pstate_get_min_max().
Also when "policy->policy == CPUFREQ_POLICY_PERFORMANCE", then
no need to do calculations as the limits will be forced anyway.
Also corrected filename in the header.Signed-off-by: Srinivas Pandruvada
Acked-by: Viresh Kumar
Signed-off-by: Rafael J. Wysocki
09 Apr, 2013
1 commit
-
The current calculation of the delay time is wrong and a cut and
paste error from a previous experimental driver. This can result in
the timeout being set to jiffies + 1 which setup the driver to race
with itself if the APIC timer interrupt happens at just the right
time.References: https://bugzilla.redhat.com/show_bug.cgi?id=920289
Reported-by: Adam Williamson
Reported-and-tested-by: Parag Warudkar
Signed-off-by: Dirk Brandewie
Signed-off-by: Rafael J. Wysocki
25 Mar, 2013
3 commits
-
They are defined in coreboot (MSR_PLATFORM) and the other
one is already defined in msr-index.h.Let's use those.
Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Viresh Kumar
Acked-by: Dirk Brandewie
Signed-off-by: Rafael J. Wysocki -
Use the correct pstate value to calculate the effective frequency.
References: https://bugzilla.redhat.com/show_bug.cgi?id=923942
Reported-by: Satish Balay
Signed-off-by: Dirk Brandewie
Signed-off-by: Rafael J. Wysocki -
Some VMs seem to try to implement some MSRs but not all the registers
the driver needs. Check to make sure all the MSR that we need are
available. If any of the required MSRs are not available refuse to
load.References: https://bugzilla.redhat.com/show_bug.cgi?id=922923
Reported-by: Josh Stone
Signed-off-by: Dirk Brandewie
Acked-by: Viresh Kumar
Signed-off-by: Rafael J. Wysocki
07 Mar, 2013
2 commits
-
It seems some VMs support the P state MSRs but return zeros. Fail
gracefully if we are running in this environment.References: https://bugzilla.redhat.com/show_bug.cgi?id=916833
Reported-by: Josh Boyer
Signed-off-by: Dirk Brandewie
Acked-by: Viresh Kumar
Signed-off-by: Rafael J. Wysocki -
If cpufreq_register_driver() fails just free memory that has been
allocated and return. intel_pstate_exit() function is removed since we
are built-in only now there is no reason for a module exit procedure.Reported-by: Konrad Rzeszutek Wilk
Signed-off-by: Dirk Brandewie
Acked-by: Viresh Kumar
Signed-off-by: Rafael J. Wysocki
16 Feb, 2013
1 commit
-
When intel_pstate is configured into the kernel it will become the
preferred scaling driver for processors that it supports. Allow the
user to override this by adding:
intel_pstate=disable
on the kernel command line.Signed-off-by: Dirk Brandewie
Signed-off-by: Rafael J. Wysocki
12 Feb, 2013
1 commit
-
Fixes 32 bit build.
on i386:
drivers/built-in.o: In function `intel_pstate_timer_func':
intel_pstate.c:(.text+0x4ce97e): undefined reference to `__udivdi3'
drivers/built-in.o: In function `intel_pstate_cpu_init':
intel_pstate.c:(.cpuinit.text+0x974): undefined reference to `__udivdi3'Reported-by: Randy Dunlap
Signed-off-by: Dirk Brandewie
Signed-off-by: Rafael J. Wysocki
09 Feb, 2013
1 commit
-
Add a P-state driver for the Intel Sandy bridge processor. In cpufreq
terminology this driver implements a scaling driver with an internal
governor.When built into the the kernel this driver will be the preferred
scaling driver for Sandy bridge processors.In addition to the interfaces provided by the cpufreq subsystem for
controlling scaling drivers. The user may control the behavior of the
driver via three sysfs files located in
"/sys/devices/system/cpu/intel_pstate".max_perf_pct: limits the maximum P state that will be requested by
the driver stated as a percentage of the avail performance.min_perf_pct: limits the minimum P state that will be requested by
the driver stated as a percentage of the avail performance.no_turbo: limits the driver to selecting P states below the turbo
frequency range.Signed-off-by: Dirk Brandewie
Acked-by: Viresh Kumar
Signed-off-by: Rafael J. Wysocki