rq_stats: add report_load_at_max_freq to the header file.
rq_stats: don't need to call the update_average_load every POSTCHANGE…
… transition, specially because we're already calling update_average_load every msecs_to_jiffies(HZ) from the Hotplug driver. With all the locks & unlocks involved plus all the time calling and making some calculations (divisions as well) we may as well don't have the stats driver to call it that much.
mako_hotplug: add hooks so that the driver and the sysfs are synchron…
…ized with the defaults if I decide to change them in the future.
mako_hotplug: fix a bug where the counter could be 10 sometimes and w…
…hen trying to write to history_load[10] it derped big time. Also add all the stats to the struct, its cleaner.
mako_hotplug: change the load history mechanism a little but based on…
… one TI patch for interactive called timer_view that makes use of this type of ringbuffers.
mako_hotplug: if the user has lots of widgets in the lock screen and …
…in the home screen the device will lag during unlock if its only single core, so revert partially the last patch.
mako_hotplug: add level for early_suspend struct.
mako_hotplug: some performance optimizations.
mako_hotplug: well duh, with the msleep if a user locked&unlocked too…
… fast it would be stuck with black screen until the msleep was finished.
mako_hotplug: change the load thresholds for a more resonable cores o…
…nline/offline. Also added a 4th check that prevents the driver to offline the second core if the load is above the first_threshold and we have 2 cores online because that means we're interacting with the device and we want to maintain some kind of fluidity and also saving some cycles by not offlining and onlining all the time.
cpufreq:interctive updates for _mako_hotplug
mako_hotplug: major re-design of the Hotplug routines based on users …
…feedback. Better handling of touch input boosts, either by frequency and/or by onlining a second core to handle a second thread while interacting with the UI. The driver is a little bit more intelligent now and reacts more appropriately on load changes. Also added two new tunables called cores_on_touch (number of cores we want the driver to online when swipping the screen) and a fourth_level which is a new lowest load threshold available to offline all cores.
cpufreq: interactive: add tunable to enable/disable dynamic_scaling o…
…f the governor tunables. I had to add some hooks around where I made to scale. Its a bit ugly code, but it works.
mako_hotplug: obvious code path optimisations. Also fix a bug where m…
…in_sample_time could get stuck to 500ms and that sucks.
mako_hotplug: some nice improvements
- automatically online a cpu with a boosted frequency instead of waiting
a sample for recalculation of load bla bla. If a core goes online it should be
because there is a bigger load so to save ms and to get better performance
the core comes online boosted to hispeed_freq that comes from interactive gov;

- wait 5 seconds before scaling up interactive tunables on high load. Sometimes
just by interacting with the UI around we can *ocasionally* have the four cores
online, but we don't really need the high performance tunables. If we're gaming
we'll hit this 5 seconds easily;

- new first_level default, decreased from 90 to 80;
mako_hotplug: if the cores go online one by one we still want the performance tunables if we hit the second level threshold with all the cores online for at least 5 seconds.
mako_hotplug: adapt according to the new interactive code.
cpufreq: interactive: fix a bug and remove some
latest ondemand from francos mako kernel
disable a few governos, keep smartmax, interactive and ondemand