"Woodruff, Richard" <r-woodruff2@xxxxxx> writes: >>In fact, you wouldn't even need a custom governor. >> To avoid governor picking overdrive OPP: >> >> # echo 550000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq >> >> To allow overdrive: >> >> # echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq > > Sure. Now is someone going to fix up every root file system which users have around. I'm not suggesting this as the standard way. The point was to say that a custom governor is not the only way. > It would be better to init the limit in the driver for this version of OMAP. Agreed. CPUfreq policy is just as easily set in the kernel at init time. Then the default would be set right, and the rootfs would be left to change it if desired. Kevin > Even if you do that someone still needs to turn on and off the limit > dynamically or create a custom governor. > > Until that kind of smart control is pervasive it is safer to just put the interface a layer down for expert use. > > But like I was saying, people are free to set the clock to what ever they want. On a properly characterized part it might even be safe for many years. A 3440 will sit well above 600MHz in nominal. > > Regards, > Richard W. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
