summaryrefslogtreecommitdiffstats
path: root/keyboards/ergodox_ez/config.h
diff options
context:
space:
mode:
authorMichael Graf <michael.trunner@seitenbau.com>2018-11-20 15:55:35 +0100
committerMichael Graf <michael.trunner@seitenbau.com>2018-11-20 15:55:35 +0100
commitad91454574ad1f0fad73923d04d6d1e037e45fed (patch)
tree9a6f73f899920cef172e9ec90b0aeaf4cedc3c40 /keyboards/ergodox_ez/config.h
parent385de70e4d81670ea12526722b78de9521465da9 (diff)
Adaptive debounce logic
The debounce filtering reports a key/switch change directly, without any extra delay. After that the debounce logic will filter all further changes, until the key/switch reports the same state for the given count of scans. So a perfect switch will get a short debounce period and a bad key will get a much longer debounce period. The result is an adaptive debouncing period for each switch. This value defines how often the same key/switch state has to be detected in successive reads until the next key state can be reported. In other words this value defines the minimum debouncing period for a switch.
Diffstat (limited to 'keyboards/ergodox_ez/config.h')
-rw-r--r--keyboards/ergodox_ez/config.h17
1 files changed, 10 insertions, 7 deletions
diff --git a/keyboards/ergodox_ez/config.h b/keyboards/ergodox_ez/config.h
index 7a350183b1..ee768853a9 100644
--- a/keyboards/ergodox_ez/config.h
+++ b/keyboards/ergodox_ez/config.h
@@ -85,17 +85,20 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
#define RGBW 1
-/* "debounce" is measured in keyboard scans. Some users reported
- * needing values as high as 15, which was at the time around 50ms.
+/*
+ * The debounce filtering reports a key/switch change directly,
+ * without any extra delay. After that the debounce logic will filter
+ * all further changes, until the key/switch reports the same state for
+ * the given count of scans.
+ * So a perfect switch will get a short debounce period and
+ * a bad key will get a much longer debounce period.
+ * The result is an adaptive debouncing period for each switch.
+ *
* If you don't define it here, the matrix code will default to
* 5, which is now closer to 10ms, but still plenty according to
* manufacturer specs.
- *
- * Default is quite high, because of reports with some production
- * runs seeming to need it. This may change when configuration for
- * this is more directly exposed.
*/
-#define DEBOUNCE 15
+#define DEBOUNCE 10
#define USB_MAX_POWER_CONSUMPTION 500