diff options
| author | Sameer Nanda <snanda@chromium.org> | 2013-02-26 11:55:45 -0800 |
|---|---|---|
| committer | ChromeBot <chrome-bot@google.com> | 2013-02-26 13:19:51 -0800 |
| commit | 9a1fc51fafbf862c26a32750ef333cf485902cea (patch) | |
| tree | d3ff3650d17fd4dccd1c512eac77d6483710e93d | |
| parent | 2cf4d02acdd3ca3eec4a925666e839f0de23c0b0 (diff) | |
| download | chrome-ec-9a1fc51fafbf862c26a32750ef333cf485902cea.tar.gz | |
temp_metrics: use iotools wrmsr instead of wrmsr
Use the "iotools wrmsr" command instead of the wrmsr alias since iotools
ebuild no longer installs the symlinks by default.
BUG=chromium-os:39180
TEST=On a Pixel issue "sudo start temp_metrics" and check
/var/log/messages to ensure that no new messages such as "init:
temp_metrics main process ended, respawning" show up.
BRANCH=none
Change-Id: I46cd8770c7e6c1af1affe8e2100033a29b9a90bb
Signed-off-by: Sameer Nanda <snanda@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/44073
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
| -rw-r--r-- | util/temp_metrics.conf | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/util/temp_metrics.conf b/util/temp_metrics.conf index 394425c1f7..307938d019 100644 --- a/util/temp_metrics.conf +++ b/util/temp_metrics.conf @@ -158,13 +158,13 @@ script set_duty_cycle() { duty_cycle=$1 for i in 0 1 2 3; do - wrmsr $i 0x19a $duty_cycle + iotools wrmsr $i 0x19a $duty_cycle done } set_pkg_power_limit() { pwr_limit=$1 - wrmsr 0 0x610 $pwr_limit + iotools wrmsr 0 0x610 $pwr_limit } log_message() { @@ -193,7 +193,7 @@ script thermal_loop() { # Hack to reset turbo activation threshold since BIOS can change it # underneath us. - wrmsr 0 0x64c 0x12 + iotools wrmsr 0 0x64c 0x12 skin_temp=$1 if [ $skin_temp -gt $TEMP_THRESHOLD_3 ]; then |