[KERNEL][N5][L] hellsCore | b26-L

-New governor: hellsactive*
-cpufreq patches (logic and leaks, typos)
-some fixes here and there
-msm-sleeper: save previous max freq
-compiled with boostedtc 4.9.2 by @aznrice2k4

*hellsactive:
-Based upon intelliactive
-removed input boost (we have an input boost in the hotplug driver)
-removed sync feature
-removed sampling down factor

Following was added:

-Align timer windows for all CPUs*
It's more advantageous to evaluate all CPUs at same time so that interactive governor gets a complete picture of the load on each CPU at a specific time. It could also reduce number of speed changes made if there are many CPUs controlled by same policy. In addition, waking up all CPUs at same time would allow the cluster to go into a deeper sleep state when it's idle.

-Reset last evaluated jiffy in idle callback*
When CPU has been busy for a long time, last evaluated jiffy will be quite behind because the timer would have been canceled. We don't want to schedule a timer to fire in the past as load will always be 100%. Reset last evaluated jiffy so that timer will be scheduled for thenext window.

-Round up timer_rate to match jiffy*
Timers are scheduled in unit of jiffies. Round up timer_rate so that it matches the actual sampling period.

-Use del_timer/add_timer_on to rearm timers*
Replace mod_timer_pinned() with del_timer(), add_timer_on(). mod_timer_pinned() always adds timer onto current CPU. Interactive governor expects each CPU's timers to be running on the same CPU. If cpufreq_interactive_timer_resched() is called from another CPU, the timer will be armed on the wrong CPU.
Replacing mod_timer_pinned() with del_timer() and add_timer_on() guarantees timers are still run on the right CPU even if another CPU reschedules the timer. This would provide more flexibility for future changes.

-Support variable frequency calculations**
Use a threshold value up to which we are evaluating the current speed weighted by current load against each new choice of speed. Above switch to the original frequency calculation proportional to load relative to the max possible frequency which allows for more dynamic and fair changes.
Default threshold is policy->min which guarantees minimal freqs and energy usage during (offloaded) media playback.
Also, choose the highest frequency below or at target, which generally saves us one freq level.

-Don't scale beyond min if the load is low***

-Thread migration commit***

I've just made some changes on commits to suit my needs.

credits:
*CAF
**myfluxi
***franciscofranco