- 16 Oct, 2013 10 commits
-
-
Srivatsa S. Bhat authored
The function update_policy_cpu() is expected to be called when the policy->cpu of a cpufreq policy is to be changed: ie., the new CPU nominated to become the policy->cpu is different from the old one. Print a warning if it is invoked with new_cpu == old_cpu, since such an invocation might hint at a faulty logic in the caller. Suggested-by:
Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by:
Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com> Acked-by:
Rafael J. Wysocki <rafael.j.wysocki@intel.com>
-
Aaro Koskinen authored
Enable cpufreq on iMac G5 (iSight) model. Tested with the 2.1 GHz version. Signed-off-by:
Aaro Koskinen <aaro.koskinen@iki.fi> Acked-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Aaro Koskinen authored
Currently cpufreq ondemand governor cannot used on older G5 models, because the transition latency is set to CPUFREQ_ETERNAL. Provide a value based on a measurement on Xserve G5, which happens to be also the highest allowed latency. Signed-off-by:
-
Aaro Koskinen authored
Some functions on switch path use msleep() which is inaccurate, and depends on HZ. With HZ=100 msleep(1) takes actually over ten times longer. Using usleep_range() we get more accurate sleeps. I measured the "pfunc_slewing_done" polling to take 300us at max (on 2.3GHz dual-processor Xserve G5), so using 500us sleep there should be fine. With the patch, g5_switch_freq() duration drops from ~50ms to ~10ms on Xserve with HZ=100. Signed-off-by:
-
Mark Langsdorf authored
Calxeda's new ECX-2000 part uses the same cpufreq interface as highbank, so add it to the driver's compatibility list. This is a minor change that can safely be applied to the 3.10 and 3.11 stable trees. Signed-off-by:
Mark Langsdorf <mark.langsdorf@calxeda.com> Acked-by:
-
Manish Badarkhe authored
Currently, code checks false return value from "regulator_set_voltage" to show failure message. Modify the code to check proper return value from "regulator_set_voltage". Signed-off-by:
Manish Badarkhe <badarkhe.manish@gmail.com> Acked-by:
-
Evgeny Kapaev authored
As per coding style, braces {} are not necessary for single statement block Signed-off-by:Evgeny Kapaev <orener300@gmail.com> Acked-by:
-
Viresh Kumar authored
policy->cur is now set by cpufreq core when cpufreq_driver->get() is defined and so drivers aren't required to set it. When space_id is ACPI_ADR_SPACE_SYSTEM_IO for acpi cpufreq driver it doesn't set ->get to a valid function pointer and so policy->cur is required to be set by driver. This is already followed in acpi-cpufreq driver. This patch adds a comment describing why we need to set policy->cur from driver. Suggested-by:
-
Sudeep KarkadaNagesha authored
Currently clk_get_sys is used with cpu-cluster.<n> as the device id which is incorrect. It should be connection/consumer ID instead. It is possible to specify input clock in the cpu device node along with the optional clock-name. clk_get_sys can't handle that. This patch replaces clk_get_sys with clk_get to extend support for clocks specified in the device tree cpu node. Signed-off-by:
Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com> Acked-by:
-
Jungseok Lee authored
This patch adds freq_attr to show a list of exynos5440 scaling available frequencies through sysfs. Common exynos driver already supports this attribute. Signed-off-by:
Jungseok Lee <jays.lee@samsung.com> Signed-off-by:
-
- 15 Oct, 2013 30 commits
-
-
Viresh Kumar authored
Fix build breakage introduced by commit 22c8b4f1 (cpufreq: sa11x0: Expose frequency table). [rjw: Changelog] Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. This also rearranges the code a bit to make it more sensible. Also removes some unnecessary checks. Cc: Santosh Shilimkar <santosh.shilimkar@ti.com> Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. This driver wasn't setting transition_latency and so is getting set to 0 by default. Lets mark it explicitly by calling the generic routine with transition_latency as 0. Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Signed-off-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Cc: Sekhar Nori <nsekhar@ti.com> Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Cc: Mikael Starvik <starvik@axis.com> Signed-off-by:
Jesper Nilsson <jesper.nilsson@axis.com> Signed-off-by:
-
Viresh Kumar authored
Use generic cpufreq_generic_init() routine instead of replicating the same code here. Cc: Shawn Guo <shawn.guo@linaro.org> Signed-off-by:
-
Viresh Kumar authored
CONFIG_CPU_FREQ_TABLE will be always enabled when cpufreq framework is used, as cpufreq core depends on it. So, we don't need this CONFIG option anymore as it is not configurable. Remove CONFIG_CPU_FREQ_TABLE and update its users. Signed-off-by:
-
Viresh Kumar authored
Many CPUFreq drivers for SMP system (where all cores share same clock lines), do similar stuff in their ->init() part. This patch creates a generic routine in cpufreq core which can be used by these so that we can remove some redundant code. Signed-off-by:
-
Viresh Kumar authored
Many common initializations of struct policy are moved to core now and hence this driver doesn't need to do it. This patch removes such code. Most recent of those changes is to call ->get() in the core after calling ->init(). Signed-off-by:
-
Viresh Kumar authored
Many common initializations of struct policy are moved to core now and hence this driver doesn't need to do it. This patch removes such code. Most recent of those changes is to call ->get() in the core after calling ->init(). Cc: Stephen Warren <swarren@nvidia.com> Signed-off-by:
-
Viresh Kumar authored
Many common initializations of struct policy are moved to core now and hence this driver doesn't need to do it. This patch removes such code. Most recent of those changes is to call ->get() in the core after calling ->init(). Cc: David S. Miller <davem@davemloft.net> Signed-off-by:
-
Viresh Kumar authored
Many common initializations of struct policy are moved to core now and hence this driver doesn't need to do it. This patch removes such code. Most recent of those changes is to call ->get() in the core after calling ->init(). Signed-off-by:
-
Viresh Kumar authored
Many common initializations of struct policy are moved to core now and hence this driver doesn't need to do it. This patch removes such code. Most recent of those changes is to call ->get() in the core after calling ->init(). Cc: Paul Mundt <lethal@linux-sh.org> Signed-off-by:
-
Viresh Kumar authored
Many common initializations of struct policy are moved to core now and hence this driver doesn't need to do it. This patch removes such code. Most recent of those changes is to call ->get() in the core after calling ->init(). Signed-off-by:
-
Viresh Kumar authored
Many common initializations of struct policy are moved to core now and hence this driver doesn't need to do it. This patch removes such code. Most recent of those changes is to call ->get() in the core after calling ->init(). Cc: Russell King <linux@arm.linux.org.uk> Signed-off-by:
-
Viresh Kumar authored
Many common initializations of struct policy are moved to core now and hence this driver doesn't need to do it. This patch removes such code. Most recent of those changes is to call ->get() in the core after calling ->init(). Cc: Kukjin Kim <kgene.kim@samsung.com> Signed-off-by:
-
Viresh Kumar authored
Many common initializations of struct policy are moved to core now and hence this driver doesn't need to do it. This patch removes such code. Most recent of those changes is to call ->get() in the core after calling ->init(). Cc: Kukjin Kim <kgene.kim@samsung.com> Signed-off-by:
-
