Re: [PATCH 1/2] cpufreq: Improve debug prints

2012-10-17 Thread Sudeep KarkadaNagesha
On 17/10/12 10:39, Viresh Kumar wrote: On 17 October 2012 14:55, Sudeep KarkadaNagesha wrote: With CONFIG_DYNAMIC_DEBUG, you can control(enable/disable) debug prints at different levels (file, module, line, function) Quickly went through this :) http://www.kernel.org/doc/ols/2009/ols2009

Re: [PATCH 1/2] cpufreq: Improve debug prints

2012-10-17 Thread Sudeep KarkadaNagesha
On 17/10/12 06:20, Viresh Kumar wrote: With debug options on, it is difficult to locate cpufreq core's debug prints. Fix this by prefixing debug prints with: "cpufreq:" With CONFIG_DYNAMIC_DEBUG, you can control(enable/disable) debug prints at different levels (file, module, line, function) R

Re: [PATCH 2/2] cpufreq: Debugging options for the cpufreq subsystem

2012-10-17 Thread Sudeep KarkadaNagesha
On 17/10/12 06:20, Viresh Kumar wrote: This adds Kconfig options for DEBUG and VERBOSE_DEBUG to the cpufreq subsystem, This is pretty useful for developers who want to debug cpufreq subsystem and don't want to editing the Makefile manually each time they want to debug. You can easily overcome t

Re: [Query]: CPUFREQ: Affected and related cpus in cpufreq

2012-10-10 Thread Sudeep KarkadaNagesha
On 10/10/12 14:26, Viresh Kumar wrote: [...] I couldn't understand the difference b/w h/w and s/w coordination. What do we mean by them here. Following patch added related related_cpu stuff: commit e8628dd06d66f2e3965ec9742029b401d63434f1 Author: Darrick J. Wong Date: Fri Apr 18 13:31:12 20

Re: [Query]: CPUFREQ: Affected and related cpus in cpufreq

2012-10-10 Thread Sudeep KarkadaNagesha
Hi Viresh, On 08/10/12 14:58, viresh kumar wrote: Hi All, Sorry for asking one of the most basic question of cpufreq :( I couldn't get the difference between affected (policy->cpus) and related cpus (policy->related_cpus) in cpufreq... As per Documentation/code: affected_cpus(policy->cpus):

[PULL REQUEST]: ARM: perf: multi-PMU support v2

2012-10-09 Thread Sudeep KarkadaNagesha
n Hunter (1): ARM: PMU: Add runtime PM Support Lorenzo Pieralisi (1): ARM: kernel: provide cluster to logical cpu mask mapping API Marc Zyngier (1): ARM: perf: add guest vs host discrimination Mark Rutland (1): ARM: perf: register cpu_notifier at driver init Su

Re: [PATCH] cpufreq: vexpress: cpufreq driver name can't be longer than 15 chars

2012-10-09 Thread Sudeep KarkadaNagesha
On 09/10/12 11:33, Amit Kucheria wrote: On Tue, Oct 9, 2012 at 2:13 PM, Jon Medhurst (Tixy) wrote: On Tue, 2012-10-09 at 09:27 +0100, Sudeep KarkadaNagesha wrote: On 09/10/12 08:10, Viresh Kumar wrote: Following is the declaration of name field in struct cpufreq_driver: char name

Re: [PATCH] cpufreq: vexpress: cpufreq driver name can't be longer than 15 chars

2012-10-09 Thread Sudeep KarkadaNagesha
e doesn't get printed properly when we do: $ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver This patch renames driver-name to fix this issue. Signed-off-by: Viresh Kumar Acked-by: Sudeep KarkadaNagesha --- drivers/cpufreq/vexpress_bL_cpufreq.c | 2 +- 1 file changed, 1 insert

[PULL REQUEST]: ARM: perf: multi-PMU support

2012-09-14 Thread Sudeep KarkadaNagesha
due to missing include of asm/pmu.h in cpu-db8500.c Jon Hunter (1): ARM: PMU: Add runtime PM Support Lorenzo Pieralisi (1): ARM: kernel: provide cluster to logical cpu mask mapping API Sudeep KarkadaNagesha (9): ARM: pmu: remove arm_pmu_type enumeration ARM: perf: move