-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate matrix_keypad linux driver #127
Comments
This is interesting, but I don't like how they turn it into keycodes; I'd rather get back the raw info of which key in the matrix was pressed and not have it impose opinions about which keys correspond to which keycodes. Is it also not possible to distinguish between key-up and key-down events? Also, this is still running in linux, and therefore susceptible to fair scheduling. We still like the PRU idea better because it's real-time, right? |
I titled this issue as "investigate" because I don't know the answers to all of those questions yet. This came as a suggestion from Frank, so I wanted to capture it so we can evaluate it at some point. |
Linux has a built-in
matrix_keypad
driver that we may be able to use for scanning and programming the keyboard matrix.Example device tree:
See
dt-bindings/input/linux-event-codes.h
.The text was updated successfully, but these errors were encountered: