On 24 May 2013 14:36, Daniel Lezcano <daniel.lezcano@xxxxxxxxxx> wrote: > I agree with Viresh, a new governor is not necessary here for that. Their patchset had two parts.. One is LAB and other is overclocking. We are trying to solve overclocking for which they never wanted a new governor. :) > There is the /sys/devices/system/cpufreq/boost option existing for x86 > platform, why do not reuse it ? It is supposed to do exactly what you > want to achieve. The problem is that it was added at the wrong place.. It should have been at cpu/cpuX/cpufreq/boost... Consider how will we achieve it for big LITTLE.. We know we can go to overdrive only for a single core in big but for two cores in LITTLE at the same time.. So, we need that in the location I just mentioned... Over that.. I believe it is governor specific too.. It shouldn't be part of conservative as it should be conservative rather then aggressive :) > IMO, the logic of boosting one core when the other are idle should be in > the driver itself and certainly not setup by the user, except if we > consider acceptable the user can burn its board ... :) I didn't get it completely.. So, with the options I gave user can only say.. boost if required and only when few cores are active. User can't just set max freq continuously if he wishes.. -- 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
