Files
OpenCellular/common
Simon Glass f3c88fa1ab 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
2012-10-31 17:21:00 -07:00
..
2012-10-24 10:09:20 -07:00
2012-10-26 09:49:38 -07:00
2012-10-26 09:49:38 -07:00
2012-07-17 13:11:44 -07:00
2012-07-17 13:11:44 -07:00
2012-10-25 11:24:04 -07:00
2012-10-24 19:07:20 -07:00
2012-10-29 16:52:49 -07:00
2012-10-25 11:24:02 -07:00
2012-10-30 15:33:25 -07:00
2012-10-25 11:23:59 -07:00
2012-10-23 17:32:01 -07:00
2012-10-23 17:32:01 -07:00
2012-10-29 16:52:49 -07:00
2012-10-29 16:52:49 -07:00
2012-10-26 09:49:38 -07:00
2012-10-25 14:12:11 -07:00
2012-10-25 14:12:10 -07:00
2012-10-25 17:03:44 -07:00
2012-08-09 17:40:37 -07:00
2012-10-29 16:52:49 -07:00
2012-10-30 12:42:43 -07:00
2012-10-29 16:52:49 -07:00
2012-10-29 16:52:49 -07:00
2012-10-26 13:10:57 -07:00
2012-10-26 09:49:37 -07:00
2012-07-23 23:30:33 -07:00
2012-10-25 17:03:44 -07:00