diff options
| author | Duncan Laurie <dlaurie@chromium.org> | 2015-09-09 14:58:52 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2015-09-10 15:40:45 -0700 |
| commit | 2a16019d548cd95776a7c60485e9cf775d8e115f (patch) | |
| tree | 6e54e5d3564fbac8fe5982cc0e0f40202911bc18 /driver/als_opt3001.c | |
| parent | dda0704bf96e04fbbe979ce721a14c3c12b8f45f (diff) | |
| download | chrome-ec-2a16019d548cd95776a7c60485e9cf775d8e115f.tar.gz | |
opt3001: Change resume hook priority
If the power rail to the ambient light sensor is only enabled
at HOOK_CHIPSET_RESUME (as on glados) then the ALS init should
not attempt to execute until after that happens.
BUG=chrome-os-partner:43493
BRANCH=none
TEST=enable ALS on glados and successfully build and use it
Change-Id: I4e8841bdf6d3970a30f58431aca771c87c7e15ba
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/298157
Reviewed-by: Alec Berg <alecaberg@chromium.org>
Diffstat (limited to 'driver/als_opt3001.c')
| -rw-r--r-- | driver/als_opt3001.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/driver/als_opt3001.c b/driver/als_opt3001.c index c2c4cc2592..712b70a00d 100644 --- a/driver/als_opt3001.c +++ b/driver/als_opt3001.c @@ -72,7 +72,7 @@ static void opt3001_init(void) if (ret) CPRINTF("ALS configure failed: ret=%d\n", ret); } -DECLARE_HOOK(HOOK_CHIPSET_RESUME, opt3001_init, HOOK_PRIO_DEFAULT); +DECLARE_HOOK(HOOK_CHIPSET_RESUME, opt3001_init, HOOK_PRIO_DEFAULT + 1); /** * Read OPT3001 light sensor data. |