| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
* Implement function rgblight_blink_layer_repeat to allow repeated blinking of one layer at a time
* Update doc
* Rework rgblight blinking according to requested change
* optimize storage
|
| |
|
| |
|
|
|
|
|
| |
* alias KEYMAP to LAYOUT
* remove KEYMAP and LAYOUT_kc
|
| |
|
|\ |
|
| | |
|
| |
| |
| | |
Co-authored-by: QMK Bot <hello@qmk.fm>
|
| | |
|
| |
| |
| | |
Co-authored-by: QMK Bot <hello@qmk.fm>
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* initial L433 commit
* change to XC
* fix L433
* disable all peripherals
* update system and peripheral clocks
* 433 change
* use its own board files
* revert its own board files
* l433 specific change
* fix stm32l432xx define
* remove duplicate #define
* fix bootloader jump
* move to L443xx and add i2c2, spi2, usart3 to mcuconf.h
* move to L443
* move to L443
* fix sdmmc in mcuconf.h
* include STM32L443
* add L443
* Include L443 in compatible microcontrollers
Co-authored-by: Nick Brassel <nick@tzarc.org>
* Include L443 in compatible microcontrollers
Co-authored-by: Nick Brassel <nick@tzarc.org>
* Update config bootloader jump description
Co-authored-by: Nick Brassel <nick@tzarc.org>
* Update ChibiOS define reasoning
Co-authored-by: Nick Brassel <nick@tzarc.org>
* Update quantum/mcu_selection.mk
Co-authored-by: Nick Brassel <nick@tzarc.org>
* fix git conflict
Co-authored-by: Nick Brassel <nick@tzarc.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Add support for MCU = STM32F446
* Update platforms/chibios/GENERIC_STM32_F446XE/configs/config.h
Co-authored-by: Nick Brassel <nick@tzarc.org>
* Restore mcuconf.h to the one used by RT-STM32F446RE-NUCLEO64
* stm32f446: update mcuconf.h and board.h for 16MHz operation, with USB enabled, and other peripherals disabled.
Co-authored-by: Nick Brassel <nick@tzarc.org>
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Tap dance callbacks may register weak mods; one case when it happens
is when a tap dance registers a key with modifiers. When the tap
dance is interrupted by pressing another key, these weak mods could
affect the interrupting key (normally any stale weak mods are cleared
at the start of action_exec() when handling a keypress event, but the
tap dance interrupt check code is called later, and the weak mods left
by that code were not cleared). Add another clear_weak_mods() call to
preprocess_tap_dance() to make sure that the interrupting keypress is
not affected by unrelated weak mods from the previous tap dance.
Fixes #12445.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(#12600)
* Add support for jumping to tinyuf2 bootloader. Adds blackpill UF2 example.
* Update flashing.md
* Update chconf.h
* Update config.h
* Update halconf.h
* Update mcuconf.h
|
| |
| |
| | |
Co-authored-by: QMK Bot <hello@qmk.fm>
|
| |
| |
| |
| |
| | |
* feat: implement leader_no_timeout logic
* docs(leader_key): infinite leader timeout docs
|
| |
| |
| | |
Co-authored-by: QMK Bot <hello@qmk.fm>
|
| | |
|
| | |
|
| |
| |
| | |
Co-authored-by: Ryan <fauxpark@gmail.com>
|
| |
| |
| | |
Co-authored-by: QMK Bot <hello@qmk.fm>
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
The dac_basic driver did not work properly with `#define AUDIO_PIN A4`
(instead of configuring the A4 pin, the driver actually was switching
the A5 pin to analog mode, breaking any other usage of that pin in
addition to emitting a distorted signal on the improperly configured
A4 pin). Fix the code to configure the A4 pin as intended.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Add missing RGB_MODE_TWINKLE / RGB_M_TW keycodes
* Better comment
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
|
| | |
|
| |
| |
| | |
Co-authored-by: QMK Bot <hello@qmk.fm>
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
* First stab at enabling builds of UF2-format binaries.
* Add description on producing a UF2 file.
|
| |
| |
| | |
Co-authored-by: QMK Bot <hello@qmk.fm>
|
|\| |
|
| | |
|
| |
| |
| |
| |
| | |
Co-authored-by: Joel Challis <git@zvecr.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Erovia <Erovia@users.noreply.github.com>
|
| | |
|
| | |
|
|\| |
|
| |
| |
| | |
Specifically, when using the Auto-Shift feature, if you hold and roll shift, it would not actually shift the character that you hit after the shift
|
|\| |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
(#12233)
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
#10199) (#11639)
* Fix handling multiples of the same MIDI note
* Extend MIDI note status to fix note releases
|
| | |
|
|\| |
|