qmk-dactyl-manuform-a/quantum/split_common
Michael Stapelberg 82aa9ad4a5
matrix: wait for row signal to go HIGH for every row (#12945)
I noticed this discrepancy (last row of the matrix treated differently than the
others) when optimizing the input latency of my keyboard controller, see also
https://michael.stapelberg.ch/posts/2021-05-08-keyboard-input-latency-qmk-kinesis/

Before this commit, when tuning the delays I noticed ghost key presses when
pressing the F2 key, which is on the last row of the keyboard matrix: the
dead_grave key, which is on the first row of the keyboard matrix, would be
incorrectly detected as pressed.

After this commit, all keyboard matrix rows are interpreted correctly.

I suspect that my setup is more susceptible to this nuance than others because I
use GPIO_INPUT_PIN_DELAY=0 and hence don’t have another delay that might mask
the problem.
2021-05-20 06:43:36 +10:00
..
eeprom-lefthand.eep
eeprom-righthand.eep
matrix.c matrix: wait for row signal to go HIGH for every row (#12945) 2021-05-20 06:43:36 +10:00
post_config.h
split_util.c Refactor of USB code within split_common (#11890) 2021-02-28 15:52:58 +00:00
split_util.h
transport.c Fix spelling mistake regarding LED Matrix in split_common. (#12888) 2021-05-14 03:37:24 +10:00
transport.h Split transport mirror (#11046) 2021-02-16 11:30:33 +11:00