| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the interest of making long-term branch maintenance incur as little
technical debt on us as possible, we should not maintain any files on
the branch we are not actually using.
This has the added effect of making it extremely clear when merging CLs
from the main branch when changes have the possibility to affect us.
The follow-on CL adds a convenience script to actually pull updates from
the main branch and generate a CL for the update.
BUG=b:204206272
BRANCH=ish
TEST=make BOARD=arcada_ish && make BOARD=drallion_ish
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I17e4694c38219b5a0823e0a3e55a28d1348f4b18
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3262038
Reviewed-by: Jett Rink <jettrink@chromium.org>
Reviewed-by: Tom Hughes <tomhughes@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Return the status of the init function. This will be used in
testing to verify that initialization was correct.
BRANCH=none
BUG=b:184856083
TEST=make buildall -j
Signed-off-by: Yuval Peress <peress@chromium.org>
Change-Id: I578b32b24b3ee59abf646307fb9670d2db74fe3b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3133624
Reviewed-by: Daisuke Nojiri <dnojiri@chromium.org>
Reviewed-by: Jeremy Bettis <jbettis@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There's a bug in the chip_revision calculation. Also, add a missing
include which causes a warning during build.
BUG=none
BRANCH=none
TEST=make buildall -j
Change-Id: Id636f4abcfffc0158d879d4b9333c7cb3ac1ee21
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3133800
Commit-Queue: Jeremy Bettis <jbettis@chromium.org>
Commit-Queue: Denis Brockus <dbrockus@chromium.org>
Tested-by: Yuval Peress <peress@chromium.org>
Auto-Submit: Yuval Peress <peress@chromium.org>
Reviewed-by: Jeremy Bettis <jbettis@chromium.org>
Reviewed-by: Denis Brockus <dbrockus@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Current software sets some registers only during initial
powering of LN9310 (when battery is plugged in). If LN9310
was reset for any reason and then a system power on was
attempted (power button press), then LN9310 would attempt a
startup without the workaround (bad idea). This change adds a
check before every LN9310 enable/disable event and
re-initializes LN9310 if a reset has occurred .
BRANCH=Trogdor
BUG=b:185308433
TEST=Should not break the current boot flow, i.e. power-up and
power-down (using long-press of the power button) should function
Change-Id: I98c08f50bfd48e09776033eac64658f6e27fb58f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2876869
Reviewed-by: John Crossley <crossley@lionsemi.corp-partner.google.com>
Reviewed-by: Wai-Hong Tam <waihong@google.com>
Commit-Queue: John Crossley <crossley@lionsemi.corp-partner.google.com>
Tested-by: John Crossley <crossley@lionsemi.corp-partner.google.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This improved workaround (compared to the previous 2520279) moves
the CFLY precharge step out of the ln9310's internal startup
sequence and implements it using I2C commands sent by the EC just before
the I2C command that triggers the ln9310 startup. The workaround
additionally modifies the ln9310's internal startup sequence to use
the precharged CFLY capacitors as decoupling of an internal node
during the startup sequence which should help prevent an OV glitch
from appearing on the LN9310 output even if the internal level
shifter on SW1 glitches and pulls up on the C1PA/B nodes.
BRANCH=Trogdor
BUG=b:185308433
TEST=Should not break the current boot flow, i.e. power-up and
power-down (using long-press of the power button) should function
similar to before this change. Testing the efficacy at preventing
the SCOUT overvoltage glitch must be done with LN9310 parts screened
out at wafer test that have a higher likelihood of exhibiting the
glitch at the SCOUT output. With these parts, startup should be
observed with a scope probe monitoring LN9310 SCOUT for overvoltagee.
Change-Id: I216991f950196225cabbbfdaa2333f1650f7f4fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2837531
Reviewed-by: Alexandru M Stan <amstan@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@google.com>
Tested-by: John Crossley <crossley@lionsemi.corp-partner.google.com>
Commit-Queue: John Crossley <crossley@lionsemi.corp-partner.google.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ln9310 driver depends on these functions (sadly), so it does not make
sense to be declaring them in board.h. Specifically, the Zephyr build
won't include Lazor's board.h.
ln9310.h is the best home I can think of for now. Ideally we could
refactor this later so that the ln9310 driver wasn't depending on
board-specific functions.
BUG=b:183054226
BRANCH=none
TEST=buildall
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I7c82d2ed3d3c16d8131238cd236741e31de5b0c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2776221
Reviewed-by: Simon Glass <sjg@chromium.org>
|
|
|
Move driver/ln9310.h to include/driver/ln9310.h so this header can be
readily included from Zephyr builds.
BUG=b:183054226
BRANCH=none
TEST=buildall
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I47c1d8dc8af90c690639ef1621cc66a9946ba40b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2776220
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@google.com>
|
