cpufreq: Reordered the CPU governors
cpufreq: InteractiveX CPU governor

Modified version of interactive with sleep+wake code
cpufreq: OnDemandX CPU governor
cpufreq: Lionheart CPU governor

A brave and agile conservative-based governor
cpufreq: SmartAssV2 CPU governor

A smart optimized governor based on OnDemand
cpufreq: LulzActive CPU governor

A new interactive governor developed by Tegrak.
For more information please visit:
http://tegrak2x.blogspot.com/2011/11/lulzactive-governor-v2.html
cpufreq: Adaptive CPU governor

This driver adds a dynamic cpufreq policy governor designed for
latency-sensitive workloads and also for demanding performance.
This governor attempts to reduce the latency of clock increases so
that the system is more responsive to interactive workloads in loweset
steady-state but to reduce power consumption in middle operation level
up will be done in step by step to prohibit system from going to max
operation level.
cpufreq: Hyper CPU governor

A tweaked OnDemand based smart and smooth optimized governor
cpufreq: BrazilianWax CPU governor

A slightly more agressive smart optimized governor
cpufreq: Intellidemand CPU governor

This is an 'ondemand' based CPU governor created by Faux123 (thanks to him for his awesome work)
cpufreq: Fix policy getting stuck when user & kernel min/max don't overlap

Every __cpufreq_set_policy starts with checking the new policy min/max has
some overlap with the current policy min/max. This works out fine until we
end up with the policy min/max being set to a range that doesn't overlap
with the user policy min/max. Once we get into this situation, the check at
the start of __cpufreq_set_policy fails and prevents us from getting out of
this state.

This only happens when one of the CPUFREQ_ADJUST/CPUFREQ_INCOMPATIBLE
notifiers called inside __cpufreq_set_policy pick a min/max outside the
range of user policy min/max.

The real intent of the check at the start of __cpufreq_set_policy is to
make sure userspace can't set user policy min > user policy max. Since
__cpufreq_set_policy always gets called only with current user policy
min/max except when the actual user space policy min/max is changed, we can
fix the issue by simply checking the new policy min/max against current
user policy min/max.

Change-Id: Iaac805825e64d7985c41fb9052bd96baacdf3d6f
Signed-off-by: Saravana Kannan <skannan@codeaurora.org>