| 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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Switch the host tests and posix-ec build to Zephyr v2.6.
Note: need to disable one assert in the hooks test until b/195971523
is resolved.
BUG=b:195571108,b:195971523
BRANCH=none
TEST=zmake testall
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I01b386b2f54cf5b752bede707ff9fbda0faad80a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3072414
Reviewed-by: Fabio Baltieri <fabiobaltieri@google.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Convert Zephyr tests from device_get_binding to DEVICE_DT_GET.
BRANCH=none
BUG=none
TEST=cq dry drun
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Change-Id: I0da71b58d70c66bf68503b7c80e57051aace60c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2985465
Reviewed-by: Yuval Peress <peress@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, every project will need to provide a custom mapping header
for i2c as well as gpios. We'd like to move that overhead to the dts
files, which will make the board dts a lot more reusable as well as
clean up the bringup of new boards.
Add to the i2c_ports enum from the dts named i2c port list. Each enum
is only added if a node exists using that enum. This also allowes for
verifying that the enum is only used once.
BRANCH=none
BUG=b:184786824
TEST=build and flashed volteer
TEST=zmake testall
Signed-off-by: Yuval Peress <peress@chromium.org>
Change-Id: I42cc098a9badac57a3781fa9dfaf32c0ec0c5aca
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2780838
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the same spacing (tab) for the i2c and i2c_dts overlay.dts files.
BRANCH=none
BUG=none
TEST=zmake testall
Signed-off-by: Yuval Peress <peress@chromium.org>
Change-Id: I4e84ab626a2eb9a9eded304ef13153962cf863f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2811184
Reviewed-by: Simon Glass <sjg@chromium.org>
Commit-Queue: Simon Glass <sjg@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Drop support for Zephyr OS v2.4 on all boards, since the v2.5 uprev is
successful.
If someone still needs to manually compile for v2.4 for testing, one
can do so by passing --zephyr-base=$PATH_TO_ZEPHYR_24 and
--ignore-unsupported-zephyr-version to zmake.
BUG=b:180409973
BRANCH=none
TEST=zmake testall
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I0b3922c0b7f47811b26bad4e7f99125cabdaed91
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2715345
Commit-Queue: Simon Glass <sjg@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Zephyr v2.5 will build for all projects now, mark it as supported for
all projects and it will be enabled by default.
We can delete v2.4 from this list once v2.5 gets a bit more battle
testing.
If you need to build for v2.4 in the interim, you should pass the
--zephyr-base flag to zmake, like so:
$ zmake --zephyr-base ~/trunk/src/third_party/zephyr/main/v2.4 ...
BUG=b:180409973
BRANCH=none
TEST=zmake testall
TEST=flash on delbin, test UART console functioning
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I9cb7902455b2c6f231bea5c0b08b0e18bca0ddd8
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2705192
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allow board-specific DTS overlays to be placed at
zephyr/dts/board-overlays/${BOARD}.dts in any module. Zmake will find
the file and append it to the DTC_OVERLAY_FILE list when discovered.
BUG=b:179491802
BRANCH=none
TEST=provided unit test passes
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I53d4a04b6056689696b4615b5998937dbcf801c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2678795
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Many of the options in CMakeLists.txt and prj.conf are no longer
necessary with zmake and Kconfig handling them automatically now.
BUG=b:178220157
BRANCH=none
TEST=`zmake testall`
Signed-off-by: Paul Fagerburg <pfagerburg@google.com>
Change-Id: I845f42c4b51214f28ab7771734232fec763c04f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2645696
Commit-Queue: Paul Fagerburg <pfagerburg@chromium.org>
Commit-Queue: Jack Rosenthal <jrosenth@chromium.org>
Tested-by: Paul Fagerburg <pfagerburg@chromium.org>
Reviewed-by: Jack Rosenthal <jrosenth@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename the node definition and instance to named-i2c-ports. This
matches the node name and other references in the code.
BUG=none
TEST=zmake testall
BRANCH=none
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Change-Id: I426cc29073d1725c208e151d0deeb9d5214bf7ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2638253
Reviewed-by: Keith Short <keithshort@chromium.org>
|
|
|
Previous Git history can be found here:
https://chromium.googlesource.com/chromiumos/platform/zephyr-chrome/+log/cc6e5d19939c03ac091b5e91d1a3b511ba99b68a/tests/dts/bindings/i2c
BUG=b:177157241
BRANCH=none
TEST=zmake testall
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I6a0d774f8400a9fd2d7a8ce7f96943b3601debe4
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2622899
Commit-Queue: Yuval Peress <peress@chromium.org>
Reviewed-by: Yuval Peress <peress@chromium.org>
|
