remove the (opp_undervolt) settings as they wont ever be used for me
remove redundent cflags-smitty
Revert "async flags from quallenge"

This reverts commit 364922cd2ade44f91e13fefb3fbbcdce3f3298c7.
Revert "Add missing mutex_unlock() call to prevent deadlocks."

This reverts commit 7e7f5830efd5028ae7616bb40a8ee6c5ddb18723.
Revert "PM-sleep-Asynchronous-threads-for-resume_noirq"

This reverts commit 2d97795869d46a6ae2a0256a84bba1b9d1dca9cd.
Revert "PM-sleep-Asynchronous-threads-for-resume_noirq"

This reverts commit 4455e9b6472d07a1f9fae9c490bc7a465a69b739.
Revert "Backport some pm functions to be ready for: Two flags for"

This reverts commit 523851c47031c05bb1d3b33808f7503027b25b99.
Revert "cpuidle: add an ignore flag to the Menu governor"

This reverts commit 6c2e17429185d075977e9e9efaff57b58588fd70.
ARM: smpboot: Enable interrupts after marking CPU online/active

With the note that we really should clean up the cpu hotplug code,
there's far too much code duplication in the arch/ implementations. The
below patch looks like it might actually work.

Thomas, others, please have a very close look because I might have
thought too hard and missed the obvious :-)

---
Subject: hotplug, sched: cpu_active vs __cpu_up
Stepan found:

CPU0		CPUn

_cpu_up()
  __cpu_up()

		boostrap()
		  notify_cpu_starting()
		  set_cpu_online()
		  while (!cpu_active())
		    cpu_relax()

<PREEMPT-out>

smp_call_function(.wait=1)
  /* we find cpu_online() is true */
  arch_send_call_function_ipi_mask()
  /* wait-forever-more */
<PREEMPT-in>
		  local_irq_enable()

  cpu_notify(CPU_ONLINE)
    sched_cpu_active()
      set_cpu_active()

Now the purpose of cpu_active is mostly with bringing down a cpu, where
we mark it !active to avoid the load-balancer from moving tasks to it
while we tear down the cpu. This is required because we only update the
sched_domain tree after we brought the cpu-down. And this is needed so
that some tasks can still run while we bring it down, we just don't want
new tasks to appear.

On cpu-up however the sched_domain tree doesn't yet include the new cpu,
so its invisible to the load-balancer, regardless of the active state.
So instead of setting the active state after we boot the new cpu (and
consequently having to wait for it before enabling interrupts) set the
cpu active before we set it online and avoid the whole mess.

Reported-by: Stepan Moskovchenko <stepanm@codeaurora.org>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
backported to linux 3.0.x by faux123
ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp

If CONFIG_SMP, cpufreq skips loops_per_jiffy update, because different
arch has different per-cpu loops_per_jiffy definition.
ARM: Fix negative idle stats for offline cpu

We see negative idle stats because of cpu dying without
cleaning up idle entry statistics. When a cpu is offline,
the most immediate thing you'd want to do is just call
into cpu_die() and not waste time calling notifier(IDLE_START).
arm: kernel: process: fix wrong macro accidently taken from 3.4 in commit 3044ee2785fd8a27830e43311a77ddcf50e4ae43