summaryrefslogtreecommitdiff
path: root/board
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2012-10-10 09:47:00 -0700
committerGerrit <chrome-bot@google.com>2012-10-31 17:21:00 -0700
commitf3c88fa1ab60101f32f9117dced3afdc3f4c9393 (patch)
treeb751fa8ac6ff6861b33a23a520c34cde1eced1cd /board
parenteee95c9448a8accc8416b32c55a89d5796cdf35b (diff)
downloadchrome-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 'board')
-rw-r--r--board/snow/ec.tasklist2
1 files changed, 1 insertions, 1 deletions
diff --git a/board/snow/ec.tasklist b/board/snow/ec.tasklist
index a07dfca87e..80d808ede9 100644
--- a/board/snow/ec.tasklist
+++ b/board/snow/ec.tasklist
@@ -19,7 +19,7 @@
TASK(VBOOTHASH, vboot_hash_task, NULL, TASK_STACK_SIZE) \
TASK(POWERLED, power_led_task, NULL, 256) \
TASK(PMU_TPS65090_CHARGER, pmu_charger_task, NULL, TASK_STACK_SIZE) \
- TASK(KEYSCAN, keyboard_scan_task, NULL, 256) \
+ TASK(KEYSCAN, keyboard_scan_task, NULL, 360) \
TASK(GAIAPOWER, gaia_power_task, NULL, TASK_STACK_SIZE) \
TASK(CONSOLE, console_task, NULL, TASK_STACK_SIZE) \
TASK(HOSTCMD, host_command_task, NULL, TASK_STACK_SIZE)