summaryrefslogtreecommitdiff
path: root/board/scarlet
diff options
context:
space:
mode:
authorparis_yeh <pyeh@google.com>2018-05-23 06:25:37 +0800
committerchrome-bot <chrome-bot@chromium.org>2018-05-30 12:50:39 -0700
commite8f009b64b0b7bedc563b55efae296e3d59a15b9 (patch)
treebadb0e7da8dde8a5576f44eef930af773e563c17 /board/scarlet
parent9102494be2821ca3bce1662d8595e8c5e0addae5 (diff)
downloadchrome-ec-e8f009b64b0b7bedc563b55efae296e3d59a15b9.tar.gz
keyboard_scan: Add option to support keyboards with language ID
ID pins are considered additional KSOs while keycode scanning works for the existing KSI0 ~ KSI7. While diriving ID pins, the state of interconnection between ID pins and KSI pins could be used for identifiers to tell keyboard itself. (e.g. US, Japan,and UK keyboard) BRANCH=master BUG=b:80168723 TEST="make -j buildall" TEST=Verified 5 distinct keyboard samples w/ different Language ID values on the same reworked Coral, which VOL_UP and VOL_DOWN were reworked for ID pins. crrev.com/c/1053617 is my experimental patch on top of this for further verification Change-Id: I1d6e647df74c50d60bc1264c045b2587d0bf23d8 Signed-off-by: paris_yeh <pyeh@google.com> Reviewed-on: https://chromium-review.googlesource.com/1068951 Commit-Ready: Paris Yeh <pyeh@chromium.org> Tested-by: Paris Yeh <pyeh@chromium.org> Reviewed-by: Paris Yeh <pyeh@chromium.org> Reviewed-by: Nicolas Boichat <drinkcat@chromium.org>
Diffstat (limited to 'board/scarlet')
0 files changed, 0 insertions, 0 deletions