board-codina-mcde: provide workaround for s6d display driver
cpufreq: interactive: revert to 31.07.2014 (from TC kernel)
Revert "cpufreq: interactive: eliminate dead band effect in low load"

This reverts commit 49fe6eadab50018bc53b84b5c93471e3a715ac25.

We are not using extended cpufreq steps. We have only around 5 cpufreq steps to cover.
As this commit makes the governor more sensitive to load changes and thus scale cpufreqs more evenly,
we will most likely end up on higher frequencies than actually needed.

Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
cpufreq: interactive: choose the highest frequency at or below target frequency

Due to our limited frequency steps, the closest frequency to target is usually higher than needed.

Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
cpufreq: interactive: Re-add cpu_online() check on governor start

I believe cpufreq still calls this for all cpus, not just online cpus.

Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
cpufreq: interactive: Uninitialise sync freq feature

This is too aggressive and will cause CPUs to increase frequencies prematurely.

Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
Revert "cpufreq: interactive: Allow 1 ms error in above_hispeed_delay comparisons"

This reverts commit ff6af80775231f1dfab8353d0b665718222218bf.

Commit ff6af807 tries to avoid a corner case where frequency is stuck in
hispeed_freq for one additional window. For example, if timer_rate is
20ms, and go_hispeed_delay is 40ms, frequency might be stuck at
hispeed_freq for 60ms due to imprecision in jiffies. Same problem can be
easily solved by making go_hispeed_delay 1ms smaller instead of changing
the code.

Change-Id: Idab7c29ed28374df219210e444454068864d144d
Signed-off-by: Junjie Wu <junjiew@codeaurora.org>