load_stats: its funny how codeaurora's original code is, it doesn't even check for changes on the max freq so if one changes the cpu max freq the policy->max of the struct is never updated and the load calculation gets derped. Also since on this Kernel the cpuinfo.max_freq is 1,7GHz we've been mistakenly calculating the load based on that frequency instead of the current max selected. Huge derp.

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