summaryrefslogtreecommitdiff
path: root/keyboards/kinesis/kint2pp/config.h
diff options
context:
space:
mode:
authorMichael Stapelberg <stapelberg@users.noreply.github.com>2021-07-01 10:07:37 +0200
committerGitHub <noreply@github.com>2021-07-01 01:07:37 -0700
commit2b8ad391aed15d41358c09d4b925e6a2bfc85ac6 (patch)
tree03db5d21acf2f9b10a6c0f2d05ef5020b474348f /keyboards/kinesis/kint2pp/config.h
parentfb405c27ad07313f5d564c02bf03130d9aaf59c7 (diff)
[Keyboard] update debounce time on kint boards (#13351)
related to https://github.com/kinx-project/kint/issues/39 related to https://github.com/qmk/qmk_firmware/pull/12626
Diffstat (limited to 'keyboards/kinesis/kint2pp/config.h')
-rw-r--r--keyboards/kinesis/kint2pp/config.h8
1 files changed, 6 insertions, 2 deletions
diff --git a/keyboards/kinesis/kint2pp/config.h b/keyboards/kinesis/kint2pp/config.h
index ff5761b6bc..a5530bc2f7 100644
--- a/keyboards/kinesis/kint2pp/config.h
+++ b/keyboards/kinesis/kint2pp/config.h
@@ -32,8 +32,12 @@
#define LED_COMPOSE_PIN C3
#define LED_PIN_ON_STATE 0
-/* Debounce reduces chatter (unintended double-presses) - set 0 if debouncing is not needed */
-#define DEBOUNCE 5
+/* Well-worn Cherry MX key switches can bounce for up to 20ms, despite the
+ * Cherry data sheet specifying 5ms. Because we use the sym_eager_pk debounce
+ * algorithm, this debounce latency only affects key releases (not key
+ * presses). */
+#undef DEBOUNCE
+#define DEBOUNCE 20
#define IGNORE_MOD_TAP_INTERRUPT