summaryrefslogtreecommitdiff
path: root/driver
diff options
context:
space:
mode:
authorRandall Spangler <rspangler@chromium.org>2013-10-23 14:28:01 -0700
committerchrome-internal-fetch <chrome-internal-fetch@google.com>2013-10-25 01:33:10 +0000
commitc8bcc57aac120ed78337e4bfa2efb9e6b4792684 (patch)
treeaafc309df70073d205184ab6c5212c563b5f2231 /driver
parent5e19f9c5d529bde4377842fc27d4d86e0b83dcf1 (diff)
downloadchrome-ec-c8bcc57aac120ed78337e4bfa2efb9e6b4792684.tar.gz
cleanup: Re-enable keyboard console channel for ARM boards
Originally, the ARM boards printed the keyboard scan matrix whenever it changed. This generated a lot of output, so we filtered that at the console channel level. When we refactored the keyboard scan module, that changed so that the scan matrix was not printed by default, and the 'ksstate' debug command was used to enable printing it. But on ARM boards, 'ksstate on' wouldn't do anything without ALSO using 'chan -1' to turn the keyboard console channel back on. And without the scan matrix printing by default, there's no reason to keep the keyboard channel off by default. BUG=chrome-os-partner:18343 BRANCH=none TEST=build all boards bang on keyboard on pit and don't see much debug output ksstate on now bang on keyboard and see matrix changes Change-Id: I554b42e7582d507530cdecad7b35df71ca0e634f Signed-off-by: Randall Spangler <rspangler@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/174373 Reviewed-by: Bill Richardson <wfrichar@chromium.org>
Diffstat (limited to 'driver')
0 files changed, 0 insertions, 0 deletions