| Message ID | 1354549282-1179-2-git-send-email-paolo.pisati@canonical.com |
|---|---|
| State | New |
| Headers | show |
diff --git a/debian.ti-omap4/config/config.common.ubuntu b/debian.ti-omap4/config/config.common.ubuntu index a4244f9..dfa10cb 100644 --- a/debian.ti-omap4/config/config.common.ubuntu +++ b/debian.ti-omap4/config/config.common.ubuntu @@ -563,7 +563,7 @@ CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m -CONFIG_CPU_FREQ_GOV_ONDEMAND=m +# CONFIG_CPU_FREQ_GOV_ONDEMAND is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m
Cpufreq in tilt-3.1 (the tree we are used to pull omap4 bits from) wasn't stable enough, and we workarounded the problem setting PERFORMANCE as the default cpu governor (see http://bugs.launchpad.net/bugs/971091). Unfortunately, some people still insist in using the broken ONDEMAND, thus to put it to rest forever, disable the compilation of the ONDEMAND governor in P. This bug was later fixed in tilt-3.4, and thus Q is not affected. BugLink: http://bugs.launchpad.net/bugs/1059555 Signed-off-by: Paolo Pisati <paolo.pisati@canonical.com> --- debian.ti-omap4/config/config.common.ubuntu | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)