Makefile: Initial support for using CS cache for CC

Codebench Sourcery toolchains are capable of using their own method
of compile caching. This patch adds initial support by allowing the
capability of using the -eabi triplet after setting PATH to link both
the cache & cc bins.

Usecase example:

  export PATH=/path-to-toolchain/bin/cache:/path-to-toolchain/bin:$PATH
  export CS_GCC_TRIPLET=arm-none-eabi-

This will probably end up in a script somewhere and probably isn't the
ideal way to implemenet this, but it is the simplest & most immediate
way I could think of.

Using a slow dual core laptop with 3GB of RAM to compile this kernel (-j4):
(results using the default -Os aren't far off)

gcc-4.7:
	-Ofast:
		Build One -
		real	32m7.383s
		user	45m34.239s
		sys	6m9.675s

		Build Two -
		real	7m20.906s
		user	6m16.320s
		sys	2m2.368s

		Build Three -
		real	6m38.865s
		user	6m2.159s
		sys	1m58.403s

Signed-off-by: Luis Cruz <ljc2491@gmail.com>
smp: Revert per-platform SMP ops

We're not quite ready for that.

Revert "ARM: smp: remove wrapper functions"

This reverts commit ff8af68d51953579c86c36f8be617f255d7ff077.

Revert "ARM: smp: Make SMP operations mandatory"

This reverts commit 1285dc90f125261eaa5fb739e52ceb3d41036e9a.

Revert "ARM: SoC: add per-platform SMP operations"

This reverts commit f6ed515b521f0501c181110b898cebeb08144b80.

Conflicts:

	arch/arm/kernel/smp.c

Revert "ARM: SoC: convert MSM to SMP operations"

This reverts commit 49e088af4f4d294ff443b1eca758a1d58ae179fa.
cpufreq: Online cpu1 when changing cpu freq

Fixes a race with Mpdecision when changing frequencies.

Signed-off-by: Luis Cruz <ljc2491@gmail.com>
cpufreq: interactive: Stop boostpulse from doing the same thing twice

Looking over this, I found that when we were boosted, we set the highspeed
freq in more places than necessary. Remove the boosted bool from
cpufreq_interactive_timer and add a check for hispeed load in the void
cpufreq_interactive_boost, so that we only need to do this check once when
boosting. If our cpu load doesn't meet hispeed_load, we simply break out
early; which should make boostpulse slightly more battery friendly.

Signed-off-by: Luis Cruz <ljc2491@gmail.com>