cpufreq: interactive: fix some choppiness

I found out why some of you say r153 might be a little choppy when opening apps
for example. This is what happens currently:

1. Touch the screen
2. If current cpu0 frequency is < input_boost_freq boost cpu0 current freq to
input_boost_freq
3. The governor checks if the is_touching is true. If its true it checks if
we're inside the 1 second window of boosted freq time after stopping touch
screen interaction
4. If we're inside the window return from the function.

This return means that while that window is true cpu0 will be blocked at
input_boost_freq, nor lower, nor higher. Sometimes some apps require more
frequency than input_boost_freq and we're bottlenecking cpu0 heavily not
letting it ramp up.

So we have to change 4. and make it like this:

4. If we're inside the window AND the new calculated freq is below
input_boost_freq (prevents cpu0 to go below the boosted freq for smoothness)
return from the function. If the new calculated freq is > than input_boost_freq
we let cpufreq do its job and ramp it up. If is_touching is still true it
won't ramp down cpu0 further than input_boost_freq.

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