HACK cpufreq: set cpuinfo_max_freq to the scaling_max_freq (thanks to @showp1984)

This prevents thermald & mpdecision from ramping cpu1 up to max.
Since this value is only read out once by them, this change will
force them to reset cpu1 to the default value instead.
Though this is not the desired outcome, it is safer than having
one core running at max clock.
Additionally this might affect apps that show the maximum
available frequency. OC apps should not be affected since
they use scaling_available_frequencies to determine the last
frequency step.

Conflicts:
	drivers/cpufreq/cpufreq.c