cpufreq: experimental 2000MHz support

Added 2 additional frequencies since testing has shown 1800MHz to be stable enough for daily use. We are simply pushing the limit to what we know can still work for some CPU's. Not all CPU's are created equal so this won't work for everyone.

Signed-off-by: sarcastillo <sar.castillo@gmail.com>

Conflicts:
	include/linux/cpufreq.h

Change-Id: I64701ac9517a55ee70d45e8d04c31342c7d33144

Conflicts:
	include/linux/cpufreq.h
block : Zen I/O scheduler

Q: What is the zen I/O scheduler?
A: Well, the question that was asked above led me to an analysis of V(R ), deadline, and some others. I already knew, but realized "this is the main feature of V(R), but wait it has no benefit to us smartphone users." So I thought about adjusting the way V(R ) handled requests and how it dispatched them (I chose V(R ) because i'd rather not tinker with a scheduler thats official and widely supported). Then I was looking over it, and realized I might as well just write a new one I don't need any of this stuff. So I came up with something awfully similar to SIO, although its a bit simpler than SIO (closer to no-op) and works just slightly different.
- It's an FCFS (First come, first serve) based algorithm. It's not strictly FIFO. It does not do any sorting. It uses deadlines for fairness, and treats synchronous requests with priority over asynchronous ones. Other than that, pretty much the same as no-op.
Updated v3.6 defconfig and build script