[Galaxy S III Original Android Development] :
Hi gokhanmoral,

A thermal control would be great in Stweaks since we can overclock to 1.8Ghz...

http://xdaforums.com/showthread.php?t=1806764

#ifdef CONFIG_EXYNOS4_SETUP_THERMAL
/* below temperature base on the celcius degree */
struct s5p_platform_tmu midas_tmu_data __initdata = {
.ts = {
.stop_1st_throttle = 78,
.start_1st_throttle = 80,
.stop_2nd_throttle = 87,
.start_2nd_throttle = 103,
.start_tripping = 110, /* temp to do tripping */
.start_emergency = 120, /* To protect chip,forcely kernel panic */
.stop_mem_throttle = 80,
.start_mem_throttle = 85,
},
.cpufreq = {
.limit_1st_throttle = 800000, /* 800MHz in KHz order */
.limit_2nd_throttle = 200000, /* 200MHz in KHz order */
},
};
#endif

Thanks to bala_gamer for this (or/and AndreiLux, don't exactly remember and I'm too lazzy to search, so sorry and thanks to both of them ;))

It's the stock thermal throttle, so for 1.4Ghz, but now we can overclock up to 1.8Ghz... so maybe a thermal control like setting the two first step would be great... stock thermal throttle when we can overclok to 1.8Ghz... Maybe it makes no sense (for some peoples maybe overclock to 1.8Ghz makes also no sense :D) but if we can manage this for benchmark (I know, I know benchs... blabla... LOL) or just for the guys who run at 1.6Ghz in "normal" use (like browsing), there is a chance they are often thermal throttled.

I do not mean to completely remove the thermal throttle or the "start emergency" (wich mean the extreme CPU temp then CPU shutdown if it reaches 120°C), but just the ability to setting the first and second steps of thermal throttling.

Given the temperatures that can support this processor (just look above), it should not be too much risk, maybe a kind of warning in your app...

Now we can manage in "real time" the CPU temp (not the battery temp!) with System Tuner for example, also link above, we could manage an hypothetic thermal throttling setting in Stweaks according to the reading of the CPU temp in "real time" with an app (maybe for advanced users??? :rolleyes:) for those who like to monitor / change settings CPU... If you can manage this in your kernel (hardcoded) then is your app with a warning (a very big warning for the noobs) it wil be awesome and we can entirely used the "high" overclock slots... :o

It can also helps about undervolting, to see if the overclocking / undervolting has an impact on CPU temperature. You can set an higher temperature limit with an higher overclock and tested your undervolt without the thought of "I tested just 5 min, otherwise my CPU will (maybe) overheated during my (stability) tests", because with thermal throttling: heat->thermal throttle->decreased CPU freq->decreased performance ... (ok, it's just an example).

Coming from the Gnex with a configurable thermal throttle or just a disabled thermal throttle (it depends of the kernel), I've never seen any problems. It helps just for guys who use their mobile hard... :D and who did (could not / would have less) decrease in performance when overclocked.

Hard to translate what I mean, I hope you understand my request or at least what I think... ;)

In any case a big thanks for your kernel! ;)