diff options
| author | Bill Richardson <wfrichar@chromium.org> | 2014-02-06 13:10:23 -0800 |
|---|---|---|
| committer | chrome-internal-fetch <chrome-internal-fetch@google.com> | 2014-02-08 04:15:39 +0000 |
| commit | 683beb87378afbebc24a41b532cb2480d90d5282 (patch) | |
| tree | 89ce40d4d5d6e20490d0176c267b7f01533a4a2d /include/button.h | |
| parent | 5c808ee56c44be4c665de6a85f5feb5cd5753f9d (diff) | |
| download | chrome-ec-683beb87378afbebc24a41b532cb2480d90d5282.tar.gz | |
Samus: Support capsense input as keyboard events.
This is experimental for now; the capsense chip simply reports its buttons
as the number keys on the keyboard (1-8).
BUG=chrome-os-partner:23382
BRANCH=samus,ToT
TEST=manual
To test, you'll need a reworked and correctly programmed capsense module.
Boot the system, and switch to VT2. Touch the capsense bar and you'll see
the input appear on the console as though you were typing numbers.
Note that the capsense hardware is still buggy. Refer to the bug for
workarounds.
Change-Id: I4c3a8b70b8197ffd538c38c59c9336383365afa7
Signed-off-by: Bill Richardson <wfrichar@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/185434
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Reviewed-by: Dave Parker <dparker@chromium.org>
Diffstat (limited to 'include/button.h')
| -rw-r--r-- | include/button.h | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/include/button.h b/include/button.h index eedf7974f8..fbfd4f3879 100644 --- a/include/button.h +++ b/include/button.h @@ -17,6 +17,14 @@ enum keyboard_button_type { KEYBOARD_BUTTON_POWER = 0, KEYBOARD_BUTTON_VOLUME_DOWN, KEYBOARD_BUTTON_VOLUME_UP, + KEYBOARD_BUTTON_CAPSENSE_1, + KEYBOARD_BUTTON_CAPSENSE_2, + KEYBOARD_BUTTON_CAPSENSE_3, + KEYBOARD_BUTTON_CAPSENSE_4, + KEYBOARD_BUTTON_CAPSENSE_5, + KEYBOARD_BUTTON_CAPSENSE_6, + KEYBOARD_BUTTON_CAPSENSE_7, + KEYBOARD_BUTTON_CAPSENSE_8, KEYBOARD_BUTTON_COUNT }; |