3.0.64
3.0.65
3.0.66-rc1
Enable USB HID
2.9.11
3.0.66
cpufreq: ondemand: Calculate gradient of CPU load to early increase frequency

Instead of checking only the absolute value of CPU load_freq to increase
frequency, we detect forthcoming CPU load rise and increase frequency
earlier.

Every sampling rate, we calculate the gradient of load_freq. If it is
too steep we assume that the load most probably will go over
up_threshold in next iteration(s) and we increase frequency immediately.

New tuners are introduced:
- early_demand: to enable this functionality (disabled by default).
- grad_up_threshold: over this gradient of load we will increase
frequency immediately.

Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
2.9.12
Captivate and Vibrant configs for 2.9.12
3.0.67
turn off some debug messages
3.0.68

Rejected:

diff a/kernel/cgroup.c b/kernel/cgroup.c	(rejected hunks)
@@ -359,12 +359,20 @@ static void __put_css_set(struct css_set *cg, int
taskexit)
 		struct cgroup *cgrp = link->cgrp;
 		list_del(&link->cg_link_list);
 		list_del(&link->cgrp_link_list);
+
+		/*
+		 * We may not be holding cgroup_mutex, and if cgrp-
>count is
+		 * dropped to 0 the cgroup can be destroyed at any
time, hence
+		 * rcu_read_lock is used to keep it alive.
+		 */
+		rcu_read_lock();
 		if (atomic_dec_and_test(&cgrp->count) &&
 		    notify_on_release(cgrp)) {
 			if (taskexit)
 				set_bit(CGRP_RELEASABLE, &cgrp->flags);
 			check_for_release(cgrp);
 		}
+		rcu_read_unlock();

 		kfree(link);
 	}
2.9.13
Merge remote-tracking branch 'sema/jb-4.2.1' into sema

Conflicts:
	arch/arm/mach-s5pv210/mach-aries.c
cpufreq: conservative: Fix sampling_down_factor
 functionality

sampling_down_factor tunable is unused since commit
8e677ce83bf41ba9c74e5b6d9ee60b07d4e5ed93 (4 years ago).

This patch restores the original functionality and documents the
tunable.

Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
cpufreq: conservative: Fix the logic in frequency
decrease checking

When we evaluate the CPU load for frequency decrease we have to compare
the load against down_threshold. There is no need to subtract 10 points
from down_threshold.

Instead, we have to use the default down_threshold or user's selection
unmodified.

Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
cpufreq: conservative: Use an inline function to evaluate

Use an inline function to evaluate freq_target to avoid duplicate code.

Also, define a macro for the default frequency step.

Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
3.0.69
2.9.15
Merge remote-tracking branch 'sema/jb-4.2.1' into sema