Comment 0 for bug 1457781

While cpufreq support on armhf is available for a while, if support is compiled as a kernel module, the corresponding module doesn't autoload by default, and thus frequency scaling is not active upon boot until a user manually load it (or until /etc/modules is modified to forcibly load it).

While in Trusty cpufreq was built-in on armhf, starting with Utopic we made support available as a kernel module, making people think that cpufreq was either broken or missing in their new kernels.

To fix it, revert back that decision and make cpufreq compiled-in again on armhf - it affects Utopic and Vivid kernels.