diff options
| author | Philip Chen <philipchen@google.com> | 2017-08-11 12:00:02 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2017-08-17 20:41:54 -0700 |
| commit | 321625dc1144ca3efef715997a09794f9fd3e9fd (patch) | |
| tree | d31b3a89e84b3e2d1de1496032404a025f528ef5 /driver/charger/rt946x.h | |
| parent | add041bd7c86e6c3d1f60caeae78af2250e825a5 (diff) | |
| download | chrome-ec-321625dc1144ca3efef715997a09794f9fd3e9fd.tar.gz | |
charger/rt946x: Finish init no matter which CHIP REV it is
When booting scarlet rev1, the initialization of rt9466
is not finished because CHIP REV < 0x05.
Actually, we shouldn't keep the latest CHIP REV in rt946x.h
because it's hard to maintain. And we should try to finish
rt946x_init() no matter what CHIP REV it is.
Also, let's clean up the logging message in rt946x_init()
a bit to make it clear that it's from RT946X.
BUG=chromium:736821, b:63739819
BRANCH=none
TEST=boot scarlet rev1 and confirm the
initialization of rt946x is finished
Change-Id: Ic0b1f837b801cc18744a1222794a055dfe8aa54c
Signed-off-by: Philip Chen <philipchen@google.com>
Reviewed-on: https://chromium-review.googlesource.com/612585
Commit-Ready: Philip Chen <philipchen@chromium.org>
Tested-by: Philip Chen <philipchen@chromium.org>
Reviewed-by: Shawn N <shawnn@chromium.org>
Diffstat (limited to 'driver/charger/rt946x.h')
| -rw-r--r-- | driver/charger/rt946x.h | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/driver/charger/rt946x.h b/driver/charger/rt946x.h index 9341f52246..027de6f15e 100644 --- a/driver/charger/rt946x.h +++ b/driver/charger/rt946x.h @@ -235,12 +235,10 @@ #if defined(CONFIG_CHARGER_RT9466) #define RT946X_CHARGER_NAME "rt9466" #define RT946X_VENDOR_ID 0x80 - #define RT946X_CHIP_REV 0x05 #define RT946X_ADDR (0x53 << 1) #elif defined(CONFIG_CHARGER_RT9467) #define RT946X_CHARGER_NAME "rt9467" #define RT946X_VENDOR_ID 0x90 - #define RT946X_CHIP_REV 0x05 #define RT946X_ADDR (0x5B << 1) #endif |