summaryrefslogtreecommitdiff
path: root/common/build.mk
diff options
context:
space:
mode:
authorVincent Palatin <vpalatin@chromium.org>2012-03-21 01:42:25 -0700
committerGerrit <chrome-bot@google.com>2012-06-22 11:34:19 -0700
commitbc672dd30c145faf427fa257b413485f80f24a78 (patch)
tree05dab70f627a4293dcd1c552fe2e265dda39633f /common/build.mk
parentb84ef3b1f2e8f266435030654976b409889a0344 (diff)
downloadchrome-ec-bc672dd30c145faf427fa257b413485f80f24a78.tar.gz
IR357x core/gfx regulator support
add function read/write the IR3570/71 voltage regulator settings. This includes new settings for the IR3571 to avoid the freeze observed on new Link boards. Currently, these settings are not flashed permanently inside the IR3571, they are just applied at CPU startup (when the VR powered). Signed-off-by: Vincent Palatin <vpalatin@chromium.org> BUG=chrome-os-partner:10171 TEST=on Link EVT, check in the kernel log that we are longer seeing the warnings from the GPU driver and the jankyness. on Link proto-1, check the IR chip version detection. Change-Id: I0781f5285aac7a9f03c7c4eb953bf97273c6d404 Reviewed-on: https://gerrit.chromium.org/gerrit/24674 Tested-by: Vincent Palatin <vpalatin@chromium.org> Reviewed-by: Bill Richardson <wfrichar@chromium.org> Commit-Ready: Vincent Palatin <vpalatin@chromium.org>
Diffstat (limited to 'common/build.mk')
-rw-r--r--common/build.mk1
1 files changed, 1 insertions, 0 deletions
diff --git a/common/build.mk b/common/build.mk
index 338a14aa24..8c282b9d84 100644
--- a/common/build.mk
+++ b/common/build.mk
@@ -14,6 +14,7 @@ common-$(CONFIG_CHARGER_BQ24725)+=charger_bq24725.o
common-$(CONFIG_PMU_TPS65090)+=pmu_tps65090.o
common-$(CONFIG_EOPTION)+=eoption.o
common-$(CONFIG_FLASH)+=flash_common.o flash_commands.o fmap.o
+common-$(CONFIG_IR357x)+=ir357x.o
common-$(CONFIG_LPC)+=port80.o host_event_commands.o
common-$(CONFIG_POWER_LED)+=power_led.o
common-$(CONFIG_PSTORE)+=pstore_commands.o