| 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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our GitLab builder uses different toolchains than the supported ones
we use for development. At present, this means that the GitLab CI
needs to call -t for each build with the desired toolchain, preventing
us from using the more general commands "zmake coverage" or "zmake
testall".
Extend the idea of toolchain in our config files to be "supported
toolchains" instead (i.e., multiple toolchains can be supported
instead of one. We do this by refactoring our toolchain support code
to consist of two related methods:
- "probe" returns True if the toolchain is detected on the system, or
False otherwise
- "get_toolchain_config" returns the BuildConfig associated with the
toolchain for the system, mirroring the functionality previously
implemented in lambda functions.
Also dropped support for arm-none-eabi, as I believe this was only
used early on during scarlet development, and am not aware of any
current users.
BUG=b:178731498
BRANCH=none
TEST=./run_tests.sh
TEST=zmake testall
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I9b2ad508ae6703f0c3b56518fc32606c0ff1777c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3134668
Commit-Queue: Jeremy Bettis <jbettis@chromium.org>
Reviewed-by: Jeremy Bettis <jbettis@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=b:193465122
BRANCH=none
TEST=build and boot to kernel without reboot issues
Signed-off-by: Denis Brockus <dbrockus@google.com>
Change-Id: I8b68d8bda4e98e8faaa6b11ccb60361527d7bab8
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3039959
Tested-by: Denis Brockus <dbrockus@chromium.org>
Auto-Submit: Denis Brockus <dbrockus@chromium.org>
Commit-Queue: Denis Brockus <dbrockus@chromium.org>
Commit-Queue: Jack Rosenthal <jrosenth@chromium.org>
Reviewed-by: Jack Rosenthal <jrosenth@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Enable PWM function on board it8xxx2_evb and hayato.
BUG=b:187189596
BRANCH=none
TEST=on it8xxx2_evb, check by oscilloscope:
1.PWM channel0 (GPA0) output frequency is same with setting 100Hz.
2.Setting PWM_POLARITY_INVERTED flag let waveform invert.
Cq-Depend: chromium:3001087
Change-Id: I7cbeb05550367b9bf346f3c85409d8259432144a
Signed-off-by: Ruibin Chang <Ruibin.Chang@ite.com.tw>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2935650
Reviewed-by: Denis Brockus <dbrockus@chromium.org>
Reviewed-by: Keith Short <keithshort@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "npcx" packer in zmake was hard-coded for Nuvoton devices.
Restructure into a new packer, BinmanPacker, which makes no Nuvoton
assumptions, and subclass it for the NpcxPacker.
Note: there's some file size check here which was coded for Nuvoton
only. I think it's not actually necessary since binman already checks
to see if the region overflowed, and will error if it did. The best
thing to do here is to keep the existing behavior and evaluate if that
Nuvoton-only size check can just be removed from zmake.
BUG=b:192401039
BRANCH=none
TEST=zmake testall
TEST=inspected fmap of hayato image, note I don't have a device to
test on right now
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: Ic45a030d0dd02451834161305f048487f7b273e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2995602
Reviewed-by: Denis Brockus <dbrockus@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add battery information so we can support charging.
BUG=b:189855648
BRANCH=none
TEST=with other CLs, build asurada for Zephyr
Signed-off-by: Simon Glass <sjg@chromium.org>
Change-Id: I638c5789a2a494bdf811c13f66d5b892f4ebded2
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2941812
Reviewed-by: Denis Brockus <dbrockus@chromium.org>
Reviewed-by: Yuval Peress <peress@chromium.org>
Commit-Queue: Denis Brockus <dbrockus@chromium.org>
Tested-by: Denis Brockus <dbrockus@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=b:189857004
BRANCH=none
TEST=zmake testall
TEST=Flash on hayato and check sensors
Signed-off-by: Denis Brockus <dbrockus@google.com>
Change-Id: I9426b5a9cb2673da0ec8280aa15768815f47014c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2934359
Tested-by: Denis Brockus <dbrockus@chromium.org>
Auto-Submit: Denis Brockus <dbrockus@chromium.org>
Reviewed-by: Yuval Peress <peress@chromium.org>
Commit-Queue: Yuval Peress <peress@chromium.org>
|
|
|
EC should boot with UART active
BUG=b:180980668
BRANCH=none
TEST=zmake configure -b $PROJ_HAYATO
Signed-off-by: Denis Brockus <dbrockus@google.com>
Change-Id: Idae8453c5803442c2f9853c45462a7eb74d5c268
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2844770
Tested-by: Denis Brockus <dbrockus@chromium.org>
Tested-by: Jack Rosenthal <jrosenth@chromium.org>
Auto-Submit: Denis Brockus <dbrockus@chromium.org>
Reviewed-by: Jack Rosenthal <jrosenth@chromium.org>
Commit-Queue: Jack Rosenthal <jrosenth@chromium.org>
|
