diff options
| author | Simon Glass <sjg@chromium.org> | 2012-10-10 09:47:00 -0700 |
|---|---|---|
| committer | Gerrit <chrome-bot@google.com> | 2012-10-31 17:21:00 -0700 |
| commit | f3c88fa1ab60101f32f9117dced3afdc3f4c9393 (patch) | |
| tree | b751fa8ac6ff6861b33a23a520c34cde1eced1cd /README | |
| parent | eee95c9448a8accc8416b32c55a89d5796cdf35b (diff) | |
| download | chrome-ec-f3c88fa1ab60101f32f9117dced3afdc3f4c9393.tar.gz | |
stm32: Implement keyscan test infrastructure
Support the keyscan test functionality on stm32.
Note: This is enabled by default so that it continues to build. But it
is unlikely that we will want this in a shipping image. I suggest we add
the facility for a dev build.
Secondly, the stack has to be larger due to a printf (which admittedly I
could just remove). Should we make the stack size conditional on the
CONFIG? Seems a bit ugly, on the other hand we don't want to waste IRAM.
BUG=chrome-os-partner:12179
BRANCH=none
TEST=manual for now:
On snow:
./ectool keyscan 20000 key_sequence.txt
See that the test passes.
Change-Id: Ic441ca0bde1be9589a924374605e2f146d16f423
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/35118
Diffstat (limited to 'README')
| -rw-r--r-- | README | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -73,3 +73,11 @@ Build Options power rails during AP startup and shutdown sequences. This is mainly useful for bringup when we don't have the corresponding sequences in the AP code. + +- CONFIG_KEYBOARD_TEST + + Turn on keyboard testing functionality. This enables a message which + received a list of keyscan events from the AP and processes them. + This will cause keypresses to appear on the AP through the same + mechanism as a normal keyboard press. + |