Revert "exynos4: Disable SW downclock in cpuidle"

This reverts commit 23f4663367ae9bdb746500703cbaeaf3bd2a0093.

I FAIL.  It turns out that I had accidentally disabled SetCPU
profile support when I implemented this patch.  After reenabling
it, I still see RCU stalls.

It turns out this is a known issue in mainline, so implementing a
proper fix.

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
arm: SMP: Fix RCU stalls due to mis-backported upstream patch

Original commit message by gokhanmoral:
missing irq_enter/irq_exit wrap around ipi_timer() after backporting of
"ARM: fix rcu stalls on SMP platforms" from Russell King.

Notes from Andrew Dodd:
Samsung backported the aforementioned patch, available here:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=7deabca0acfe02b8e18f59a4c95676012f49a304

However, 3.0.x has an additional ipi_timer() that needs to be wrapped
with irq_enter()/irq_exit(), this patch adds these.

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

arm: smp: Wrap backtrace IPI with irq_enter/exit

This appears to be something that should also be wrapped.  Also,
the backtraces experienced may be a cause and not a symptom -
instead of an RCU stall causing backtraces, backtraces
may be causing an RCU stall - which causes more backtraces
and then the system gets mental.

Change-Id: If1c24afd497dd77b0505ad6caf74216b068eed36
Signed-off-by: Andrew Dodd <atd7@cornell.edu>
mali: 3-step GPU DVFS control

Based on gokhanmoral's patch at:
https://github.com/gokhanmoral/siyahkernel3/commit/ad613cfea890fd52b3b7cd174bbe06463f6a1f39

With the following changes:
The second step in mali_dvfs (freq) should always be 1000000 for 1 MHz.  It is
not a voltage
Setup down threshold logic to be a target threshold - instead of being percentage
of current load, it is the desired percentage of load at the lower frequency.
This eliminates needing to think about whether your down_threshold will
be greater than 100% load at the new frequency.

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
gpu voltage, clock and stepcount interfaces
config: Enable GPU clock/voltage control
exynos4: hotplug: Gingerbread legacy hotplug

It seems like the existing hotplug algorithms in the ICS kernel
are not quite mature enough for production yet.  See all the hackery
needed to not get stand-hotplug to turn off the boot CPU...

This forward-ports a tuned version of the Gingerbread legacy
hotplug algorithm (includes support for screen-off profiles and
minimum hotplug frequency).

Change-Id: I22a999202e752308446244c272b23960a7b108ee
Signed-off-by: Andrew Dodd <atd7@cornell.edu>
config: Switch to Gingerbread legacy hotplug

This will hopefully work around all of the "suspend + hotplug"
wonkiness

Change-Id: If6142ad76db38a5613c0a0171bf8a38f5f136894
Build stage2 initramfs into kernel.

Instead of attaching boot and recovery initramfs to the kernel, with a
header which must be scanned for, insert them into the builtin bootstrap
initramfs as cpio images.

Change-Id: Ifbd81a30b8b2fe4f9443804a6421e083355cc5de
i777: build stage2 initramfs into kernel.

Change-Id: Ie85ea18e93a3f9463ae54d64a219d8d2c51ab640
smb136: Remove mach/gpio-p2.h include

Mach-specific includes are handled by the build system - this
conflicts with mach-q1.h

Change-Id: I04889e874720d5642991a85b6d0433fd9cba634f
config: Bring Note defconfig in line with our current state

Also fix up Note defconfig to be device-appropriate (different sensors,
etc.)

Change-Id: Id8ad1843cf8ac73342e7d713104e1935cd5fd1f1