cpufreq: interactive governor: Delete boost timer on CPUFREQ_GOV_STOP.

Concurrent execution of CPUFREQ_GOV_STOP and interactive_boost_timer()
should be avoided.
Also, interactive_boost() should follow CPUFREQ_GOV_STOP on
flush_work().

Change-Id: I53e897d5ee1834f5cbf0778dd48fc604ec3ea34d
Signed-off-by: Oleg Matcovschi <oleg.matcovschi@ti.com>
cpufreq: interactiver governor: Add a time view concept

CPUFreq governors are always a tradeoff between power vs performance.
For low power UCs we want to have a less reponsive cpufreq governor that
does not respond or react to each load pick.
However when scrolling on the screen or during webbrowsing we need a more
responsive governor that interact or esponse to each load variation.

To detect which kind of application we have, we'll rely on the history of
the load. if the the average over the load history is high that means we
need to be more responsive so we change the governor paramters in that
direction.
if the average over the load history is low thatmeans we are in low power
UCs so we change the governor parameter to be less responsive

Change-Id: Ifd55ac4cfbc1bd9eded4ae603b158054c6169e8c
Signed-off-by: Nicole Chalhoub <n-chalhoub@ti.com>
Signed-off-by: Taras Kondratiuk <taras@ti.com>
Signed-off-by: Willi Ye <williye97@gmail.com>

Conflicts:
	drivers/cpufreq/cpufreq_interactive.c