cpufreq: interactive: no need to block cpu0 frequency if its >= input_boost_freq. If we don't need to run it higher than input_boost_freq then the next freq will be input_boost_freq. This should save some battery in the long run. Thanks reborn90.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
Revert "block,elevator: use new hashtable implementation"

This reverts commit 04139d06ab75460881b557021df10c919c549f77.
Revert "hashtable: introduce a small and naive hashtable"

This reverts commit ecfd01996e71dc5eb66516d9645c9491ec82354c.
cpufreq: interactive: since cpu0 and cpu1 are always online lets also block cpu1 and lets not let him go below input_boost_freq. Also add some changes picked from some commits from Google: one bit is to prevent the timer to run if the cpu is offline, thus the early return. No need to waste resources running a function in a dead cpu. Also delete the timer on idle_start on offline cpus. Used mod_timer_pinned instead of mod_timer so that the timers don't migrate from cpu to cpu, they should only run on the designated cpus on GOV_START.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
cpufreq: interactive:  why was this duplicate code merged?

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
tegra: rq_stats: in my opinion iowait should not be counted as idle time, so subtract iowait from idle on the load calculations.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>