my qmk configs http://archive.git.mgrote.net/qmk_sweep_skeletyl/atom?h=master 2025-11-11T12:35:03+00:00 2025-11-11T12:35:03+00:00 Stefan Kerkmann 2025-11-11T12:35:03+00:00 urn:sha1:c68e4dec10db07f16f6d2b5dd883bbcfc09cde25 * suspend: suppress wake up keypress Waking the host from suspend is done by pressing any key on the keyboard, the regular key codes assigned to the keys are not important and must not be sent - otherwise they usually end up in password prompts as ghost characters that have to be deleted again. This commit adds suppression for all keys pressed at the time of wake up. Once a key is released it functions as a regular key again. Signed-off-by: Stefan Kerkmann <karlk90@pm.me> * suspend: update wake up matrix after wake up delay If USB_SUSPEND_WAKEUP_DELAY is set, the keyboard sleeps during wake up - which can be up to multiple seconds. To handle key presses and releases in that time frame we have to handle the following cases: 1. Key not pressed before suspend, and not pressed after wakeup → do nothing (normal case). 2. Key not pressed before suspend, but pressed after wakeup → set the wakeup_matrix bit to 1 (so that the press and release events would be suppressed). 3. Key pressed before suspend, but not pressed after wakeup → do nothing (the release event will be generated on the first matrix_task() call after the wakeup). 4. Key pressed before suspend, and still pressed after wakeup → do nothing (the release event will be generated some time later). Signed-off-by: Stefan Kerkmann <karlk90@pm.me> Co-authored-by: Sergey Vlasov <sigprof@gmail.com> * keyboards: anavi: macropad8: disable snake and rgb_test effects ...to shrink the binary size. 2025-06-27T07:17:28+00:00 Joel Challis 2025-06-27T07:17:28+00:00 urn:sha1:bc5c5e3251d019f3e070d7ea9e5c77501b25738d 2025-05-11T22:38:48+00:00 Joel Challis 2025-05-11T22:38:48+00:00 urn:sha1:88c094908bb94324e28876f2beb8028a9fad086d 2024-10-18T07:57:08+00:00 Stefan Kerkmann 2024-10-18T07:57:08+00:00 urn:sha1:3f9d4644126483bbd937f2be75a8878a1c986630 * usb_device_state: add idle_rate, led and protocol Previously all usb drivers and platform implementations (expect for our oddball atsam) tracked the same two global variables: - keyboard_protocol: to indicate if we are in report or boot protocol - keyboard_idle: for the idle_rate of the keyboard endpoint And a local variable that was exposed trough some indirection: - keyboard_led_state: for the currently set indicator leds (caps lock etc.) These have all been moved into the usb_device_state struct wich is accessible by getters and setters. This reduces code duplication and centralizes the state management across platforms and drivers. Signed-off-by: Stefan Kerkmann <karlk90@pm.me> * usb_device_state: reset protocol on reset The usb hid specification section 7.2.6 states: When initialized, all devices default to report protocol. However the host should not make any assumptions about the device’s state and should set the desired protocol whenever initializing a device. Thus on reset we should always do exactly that. Signed-off-by: Stefan Kerkmann <karlk90@pm.me> * keyboards: fix oversize warnings Signed-off-by: Stefan Kerkmann <karlk90@pm.me> --------- Signed-off-by: Stefan Kerkmann <karlk90@pm.me> 2024-07-05T11:02:39+00:00 Joel Challis 2024-07-05T11:02:39+00:00 urn:sha1:d0e89aeccada3f0df906dd4ff8fa7708b0d8234e 2024-04-24T18:33:52+00:00 Joel Challis 2024-04-24T18:33:52+00:00 urn:sha1:16cca527a6b46c2aa365428d7d1e214509068c4a 2024-03-14T10:45:12+00:00 Joel Challis 2024-03-14T10:45:12+00:00 urn:sha1:63dd131d812be4b8d4894fc20ca9968e25996b07 2024-01-09T14:01:34+00:00 Joel Challis 2024-01-09T14:01:34+00:00 urn:sha1:b6b3efc14b21117d13ae33a2eda96c5647817d5b 2023-10-23T04:43:46+00:00 Ryan 2023-10-23T04:43:46+00:00 urn:sha1:0c160e1fbafbf477c74e64fd8ab9a9121eb0f42a 2023-07-07T11:24:07+00:00 Ryan 2023-07-07T11:24:07+00:00 urn:sha1:30de598650f368e215ad5f82c7b9de52eceb539e