diff options
author | Jack Rosenthal <jrosenth@chromium.org> | 2021-11-04 12:11:58 -0600 |
---|---|---|
committer | Commit Bot <commit-bot@chromium.org> | 2021-11-05 04:22:34 +0000 |
commit | 252457d4b21f46889eebad61d4c0a65331919cec (patch) | |
tree | 01856c4d31d710b20e85a74c8d7b5836e35c3b98 /docs/zephyr_poc_device_bringup.md | |
parent | 08f5a1e6fc2c9467230444ac9b582dcf4d9f0068 (diff) | |
download | chrome-ec-stabilize-14438.B-ish.tar.gz |
ish: Trim down the release branchstabilize-wristpin-14469.59.B-ishstabilize-voshyr-14637.B-ishstabilize-quickfix-14695.187.B-ishstabilize-quickfix-14695.124.B-ishstabilize-quickfix-14526.91.B-ishstabilize-14695.85.B-ishstabilize-14695.107.B-ishstabilize-14682.B-ishstabilize-14633.B-ishstabilize-14616.B-ishstabilize-14589.B-ishstabilize-14588.98.B-ishstabilize-14588.14.B-ishstabilize-14588.123.B-ishstabilize-14536.B-ishstabilize-14532.B-ishstabilize-14528.B-ishstabilize-14526.89.B-ishstabilize-14526.84.B-ishstabilize-14526.73.B-ishstabilize-14526.67.B-ishstabilize-14526.57.B-ishstabilize-14498.B-ishstabilize-14496.B-ishstabilize-14477.B-ishstabilize-14469.9.B-ishstabilize-14469.8.B-ishstabilize-14469.58.B-ishstabilize-14469.41.B-ishstabilize-14442.B-ishstabilize-14438.B-ishstabilize-14411.B-ishstabilize-14396.B-ishstabilize-14395.B-ishstabilize-14388.62.B-ishstabilize-14388.61.B-ishstabilize-14388.52.B-ishstabilize-14385.B-ishstabilize-14345.B-ishstabilize-14336.B-ishstabilize-14333.B-ishrelease-R99-14469.B-ishrelease-R98-14388.B-ishrelease-R102-14695.B-ishrelease-R101-14588.B-ishrelease-R100-14526.B-ishfirmware-cherry-14454.B-ishfirmware-brya-14505.B-ishfirmware-brya-14505.71.B-ishfactory-kukui-14374.B-ishfactory-guybrush-14600.B-ishfactory-cherry-14455.B-ishfactory-brya-14517.B-ish
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>
Diffstat (limited to 'docs/zephyr_poc_device_bringup.md')
-rw-r--r-- | docs/zephyr_poc_device_bringup.md | 52 |
1 files changed, 0 insertions, 52 deletions
diff --git a/docs/zephyr_poc_device_bringup.md b/docs/zephyr_poc_device_bringup.md deleted file mode 100644 index 394aa4a05b..0000000000 --- a/docs/zephyr_poc_device_bringup.md +++ /dev/null @@ -1,52 +0,0 @@ -# Zephyr Proof-of-Concept-Device Bringup - -It may be useful to build a Zephyr OS-based EC for a device which -already has a CrOS EC device build, for the purposes of demonstrating -the feasibility of Zephyr OS. - -This document is a work-in-progress list of tricks & tools that may be -useful to you. - -## Initial Bringup - -Initially, you'll want to get a basic UART functioning with nothing -but a shell and some basic console commands. - -An example CL to do this for Lazor can be found -[here](https://crrev.com/c/2749765). - -## Bringing up GPIOs - -After you have UART functioning, GPIOs can be an easy target to start -unblocking further features. - -We have a very ugly program to auto-generate the GPIO DTS based on -gpio.inc for the existing board. You can find it at -`util/gpios_to_zephyr_dts.c`, and instructions are in the file on how -to compile and use it. You may have to hand-modify the output. - -The resultant CL for Lazor can be found [here](https://crrev.com/c/2749768). - -## Bring up Host Commands - -Set `CONFIG_PLATFORM_EC_HOSTCMD=y` and enable the appropriate -host-command interface for your platform (e.g., eSPI). - -An example CL for Lazor can be found [here](https://crrev.com/c/2749428). - -As long as you get this compiling that should be enough to move to the -next step. Further testing of the host command layer will require -power sequencing up and going. - -## Enabling some simple GPIO-based buttons and switches - -Next, you can: - -* [Add the lid switch](https://crrev.com/c/2749768) -* [Add the power button](https://crrev.com/c/2749426) -* [Add AC presence detection](https://crrev.com/c/2749428) - -## Power Sequencing - -TODO(jrosenth): add steps on enabling power sequencing and expand this -document. |