drivers: thermal: msm_thermal: Expose pre_throttled_max variable to sysfs

pre_throttled_max isn't correctly grabbing the max CPU frequency before thermald throttles the CPU, so when pre_throttled_max=0, the max CPU frequency is set to 1944MHz, thus causing a reboot for the vast majority of devices that do not support 1944MHz:
[ 2887.003021] msm_thermal: ERROR! pre_throttled_max=0, falling back to 1944000
[ 2887.003265] msm_thermal: Low Thermal Throttling Ended! temp: 26
[ 2887.003692] msm_thermal: Limiting core0 max frequency to 1944000
[ 2887.003906] msm_thermal: ERROR! pre_throttled_max=0, falling back to 1944000
[ 2887.004272] msm_thermal: Low Thermal Throttling Ended! temp: 26
[ 2887.004699] msm_thermal: Limiting core1 max frequency to 1944000

As cpu_policy->cpuinfo.max_freq doesn't seem reliable (given pre_throttled_max's behavior), I have replaced cpu_policy->cpuinfo.max_freq in multiple places with pre_throttled_max.

This is a temporary workaround to the random reboots as this change requires the max CPU frequency to be set via an init.d script (in order to write the max CPU freq to pre_throttled_max). I will keep this workaround until I find the time to properly debug why the max CPU freq is being set to 1944MHz.

Signed-off-by: Sultanxda <sultanxda@gmail.com>
drivers: thermal: msm_thermal: Set allowed mid temp to 78C for consistency