mach-u1: Unmap HOME key GPIO on SGH-I777

This device doesn't have a HOME key - Having the GPIO
mapped and floating with no input leads to spurious
HOME key presses detected.

Signed-off-by: Andrew Dodd <atd7@cornell.edu>

Conflicts:

	arch/arm/mach-exynos/mach-u1.c

Change-Id: I4169258e66acd4596768868432b7cce8b3066554
u1-gpio: Add GPIO definitions for SGH-I777

Conflicts:

	arch/arm/mach-exynos/u1-gpio.c

Change-Id: I75aee5c4b67975056998e91be99ca70ff357247b
config: Update n7000 defconfig

The config item name for the wacom driver changed, wacom stuff
should work now.

Change-Id: I4ef6896ede6de3387babc0ef53404f06435e6fed
cpufreq_conservative: Change default tuning settings

Half the polling rate, but more aggressive up/down thresholds.

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
cpufreq_conservative: Bump default frequency step up to 10 from 5

Based on a better understanding of how the governor operates,
this is a better choice on most Exynos devices.

Change-Id: I8ed87e2b61f621138aa5a20951d8a70037e986a9
Signed-off-by: Andrew Dodd <atd7@cornell.edu>
cpufreq_conservative: Reduce minimum polling interval

Conservative's minimum polling interval is very long - this patch reduces
it so the user can tune it downwards, while still respecting hardware
transition_latency limits.

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
ondemand: cpuidle detection

I found a problem with the ondemand governor while in earlysuspend
suspend mode (ondemand keeping the freq close to the max at all times
despite near 0% load). The problem is that the cpu starts to go in
long cpuidle cycles, a sampling_rate of 10000 (usec) is applied only
once in a while and the real sampling_rate becomes 1 second (or more).

So when a wakeup happens we return to the 10000usec sampling rate. The
ondemand sees lots of activity after the wakeup but those "loads" must
be adjusted down if the previous wall_time delta was huge and the
current one is tiny. We're too close to long cpuidle to worry about
the cpu freq anyway and it may be just a jitter load that if we take
into account without adjusting it down, will lead to the next long
cpuidle to be entered at the max freq again, and this repeats forever.

So my solution is to tweak the ondemand to scale down the "load"
according to the decrease in the wall_time delta ratio
(deep_sleep_ratio variable). This allows the CPU to stay at the lowest
freq during the deep sleeps even when the ondemand governor is enabled
and the sampling_rate is set to 10000. (setting the sampling_rate to
values >100000 would also tend to hide the problem but it'd screw the
interactive behavior by running at the lowest frequency for too long
during interactive usage)

During interactive usage with the screen on (not in earlysuspend
mode), or during playback or voip with screen off the deep_sleep_rate
is set to 1 practically all the time so it won't alter the behavior of
the ondemand governor unless the system is very idle (and in turn when
we want it to stay at low freq).

Change-Id: If0391e6d6c41c1c8c9fa590502e88e681a800b04

Signed-off-by: Andrea Arcangeli <andrea@cpushare.com>