| 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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note that currently CONFIG_SYSCON=y is required. There's an ongoing
PR (https://github.com/zephyrproject-rtos/zephyr/pull/38762) to remove
that requirement in favor of simply detecting an enabled node in DT
via the compatible string.
BRANCH=none
BUG=b:179900857, b:165777478, b:200642229
TEST=zmake testall
Signed-off-by: Yuval Peress <peress@google.com>
Change-Id: Idad1f53afbda503e0e0b2fdf2931d5267a391d4d
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3177749
Reviewed-by: Sam Hurst <shurst@google.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The CONFIG_CROS_RTC_NPCX config defaults to 'n'. Explicitly
add CONFIG_CROS_RTC_NPCX=y to herobrine_npcx7, lazor, and trogor
devices.
BRANCH=none
BUG=b:194710429
TEST=none
Signed-off-by: Sam Hurst <shurst@google.com>
Change-Id: I7a551f5574a645ea5e1495c19ec6ed09c4866ea5
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3144534
Reviewed-by: Wai-Hong Tam <waihong@google.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename CONFIG_PLATFORM_EC_VBOOT to CONFIG_PLATFORM_EC_VBOOT_EFS2,
since this is what is actually toggled by the config.
EFS2 is only a small component of verified boot, and we have many
boards which don't actually use it (e.g., trogdor family) for verified
boot, making the existing name very confusing.
BUG=none
BRANCH=none
TEST=zmake testall
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I68ea5815b4a001c680fc78196bb7a02815799b52
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3088164
Commit-Queue: Denis Brockus <dbrockus@chromium.org>
Reviewed-by: Denis Brockus <dbrockus@chromium.org>
|
|
|
Trogdor is a reference design, which doesn't have Zephyr support yet.
Lazor is a shipping design of the Trogdor family, which already have
Zephyr support. This CL creates the Trogdor Zephyr image and modifies
the hardware difference.
The CL first copies the directory lazor/ to trogdor/.
And do the following changes:
* Rename all the board term lazor -> trogdor
* Update the GPIOs (recheck the result of gpios_to_zephyr_dts)
* Update the GPIO interrupts
* Update the battery info
* Update the sensor info
* Do not support multi-TCPM driver
* Do not include sku.c (trogdor doesn't have it yet)
BRANCH=None
BUG=b:184071830
TEST=Built the Zephyr image. Booted it on an existing Trogdor board.
Change-Id: I3b603284c719c119bb05460e7d4386d2c2eabda4
Signed-off-by: Wai-Hong Tam <waihong@google.com>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2994753
Reviewed-by: Keith Short <keithshort@chromium.org>
|
