tree 8170813278d41a03c2d511040303cdec02b1f31b
parent 883b5072d7bf5f1ab1173e1c9e394c39e39bc9bd
author Todd Broch <tbroch@chromium.org> 1374259569 -0700
committer ChromeBot <chrome-bot@google.com> 1374607548 -0700

daisy: Disable LMT from modifying max/min cpufreq.

We don't want laptop-mode tools(LMT) to manage min/max frequencies at
all.  Those limits may be set prior to LMT (see bug for details).

Additionally, thermal.sh also maintains the max value so don't want
LMT undermining that.

BUG=chrome-os-partner:18927
TEST=manual, emerge

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

And see no changes by LMT.  If I instead modify patch to use explicit
frequency (say none -> 300000) I do see LMT make the change

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  300000
  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
  300000

Original-Change-Id: Ia004d01e6ab21ae3e69a45f10c73de4ee5394c30
Reviewed-on: https://gerrit.chromium.org/gerrit/62667
Commit-Queue: Todd Broch <tbroch@chromium.org>
Tested-by: Todd Broch <tbroch@chromium.org>
Reviewed-by: Todd Broch <tbroch@chromium.org>
(cherry picked from commit c12d2ed202a61cc19d0659036448c054d520ae3f)

Change-Id: I23abd1e71c299f40a372e18e6297cdadd45afa78
Reviewed-on: https://gerrit.chromium.org/gerrit/63047
Commit-Queue: Todd Broch <tbroch@chromium.org>
Reviewed-by: Todd Broch <tbroch@chromium.org>
Tested-by: Todd Broch <tbroch@chromium.org>
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>