On Thu, 20 Jun 2013 10:31:30 +0530, Viresh Kumar wrote: > > I'd say there needs to be a separate controller/monitor for that > > that will know what the chip's thermal limit is and how that > > relates to how fast the CPU core(s) may run and for how much time. > > I'm not sure it is sufficient to "wait for thermal to kick in" > > here, because you may need to slow down things in advance (i.e. > > before thermal sensors tell you there's too much heat, because that > > may be too late already). > > That's why I wasn't sure about software boosting initially. But at > the same time a thermal sensor might be good enough. They just have > to be programmed accordingly, so that they fire a bit in advance > before things are out of control. :) I think that thermal subsystem shall disable boost when SoC is heated up. The problem is to guarantee, that thermal will be always enabled and correctly configured when software based boost is ready to run. -- Best regards, Lukasz Majewski Samsung R&D Institute Poland (SRPOL) | Linux Platform Group -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
