summaryrefslogtreecommitdiffstats
path: root/tmk_core/common
Commit message (Collapse)AuthorAgeFilesLines
* Split out arm_atsam shift register logic (#14848)Joel Challis2021-10-221-1/+7
|
* [Core] Add support for RISC-V builds and GD32VF103 MCU (#12508)Stefan Kerkmann2021-10-186-2/+176
| | | | | | | | | | | | | | | | | | | | | | | | | | | * Add support for RISC-V builds and GD32VF103 MCU * Add toolchain selection in chibios.mk based on the mcu selected in mcu_selection.mk * Reorder and added comments to chibios.mk to have a streamlined makefile * Add GD32VF103 mcu to possible targets for QMK. * Add STM32 compatibility for GD32VF103 MCU, this is hacky but more efficent then rewriting every driver. * Add GigaDevice DFU bootloader as flash target, please note that dfu-util of at least version 0.10 is needed. * Add analog driver compatibility * Add apa102 bitbang driver compatibility * Add ws2812 bitbang driver compatibility * Add eeprom in flash emulation compatibility * Allow faster re-builds with ccache * Add SiPeed Longan Nano to platform files * Add SiPeed Longan Nano Onekeys * Make quine compatible with other bootloaders * Support builds with picolibc * Add risc-v toolchain to arch and debian/ubuntu scripts
* Add HT32 support to core (#14388)bwisn2021-10-181-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | * tmk_core: temporary fix to allow HT32 based keyboards to work without patched ChibiOS-contrib (AnnePro2) * HT32: add spi support Add persistent led support with eeprom (#9) * adding HT32 support to chibios SPI master driver update spi driver, fix bad merging with master * HT32: fix formatting HT32: Fix formatting: tmk_core/protocol/chibios/usb_main.c Co-authored-by: Drashna Jaelre <drashna@live.com> * HT32: Apply suggestions from fauxpark's code review Co-authored-by: Ryan <fauxpark@gmail.com> * HT32: update spi driver * ht32: apply code review suggestions, remove old workaround Co-authored-by: tech2077 <tech2077@gmail.com> Co-authored-by: Drashna Jaelre <drashna@live.com> Co-authored-by: Ryan <fauxpark@gmail.com>
* Further tidy up of STM32 eeprom emulation (#14591)Joel Challis2021-10-161-2/+2
|
* Enable eeprom with F401xE ld (#14752)Dasky2021-10-081-3/+3
|
* Remove SERIAL_LINK feature (#14727)Joel Challis2021-10-072-2/+2
| | | | | | | | | | | | | | | | | * Remove SERIAL_LINK * more stale paths in doxygen-todo * Fix * More refs * Update testing docs * Update doxygen-todo Co-authored-by: Ryan <fauxpark@gmail.com> Co-authored-by: Ryan <fauxpark@gmail.com>
* massdrop alt/ctrl: support saving into nvm (#6068)Alexandre d'Alton2021-09-301-4/+90
| | | | | | | | | | | | | | | | | | | | | | | * support saving into SmartEEPROM Signed-off-by: Alexandre d Alton <alex@alexdalton.org> * atsam: update smarteeprom implementation - Use define for SmartEEPROM buffer address - Check buffer overflow - Do not perform operation when timeout occurs Signed-off-by: Alexandre d'Alton <alex@alexdalton.org> * return 0 instead of ff for invalid address or timeout Signed-off-by: Alexandre d'Alton <alex@alexdalton.org> * clang-format * Add extra bounds checks Co-authored-by: zvecr <git@zvecr.com>
* Merge remote-tracking branch 'origin/master' into developQMK Bot2021-09-291-3/+13
|\
| * [Core] Fix "6kro enable" and clarify naming (#14563)Drashna Jaelre2021-09-291-3/+13
| | | | | | | | | | | | | | | | | | | | | | * Fix USB_6KRO_ENABLE compilation errors * Add info to docs * Rename define to be more accurate * Remove unused rule * Refixe docs
* | Initial pass of F405 support (#14584)Joel Challis2021-09-251-2/+4
| | | | | | | | | | | | | | | | | | * Initial pass of F405 support * remove some conf files * docs * clang
* | Make ChibiOS PAL interactions less STM32 specific - Round 2 (#14456)Joel Challis2021-09-161-0/+2
| |
* | Add Support for USB programmable buttons (#12950)Thomas Weißschuh2021-09-155-2/+26
| |
* | Implement F4 eeprom (#14195)Joel Challis2021-09-152-5/+53
| |
* | Migrate STM32_EEPROM_ENABLE to use EEPROM_DRIVER (#14433)Joel Challis2021-09-152-48/+10
| |
* | Refactor use of _STM32_ defines (#14439)Joel Challis2021-09-151-12/+17
| |
* | Refactor use of STM32_SYSCLK (#14430)Joel Challis2021-09-142-8/+10
| | | | | | | | | | * Refactor use of STM32_SYSCLK * clang
* | Merge remote-tracking branch 'origin/master' into developQMK Bot2021-09-051-2/+2
|\|
| * Fix eeprom for Durgod boards (#14324)Joel Challis2021-09-051-2/+2
| |
* | Merge remote-tracking branch 'origin/master' into developQMK Bot2021-09-055-76/+119
|\|
| * Tidy up defines within STM EEPROM emulation (#14275)Joel Challis2021-09-055-76/+119
| | | | | | | | | | | | | | | | | | | | | | * Tidy up defines within stm eeprom emulation * Fix tests * Resolve todo * Still use page notion in clear * Remove more f4 refs
* | Merge remote-tracking branch 'origin/master' into developQMK Bot2021-08-304-39/+6
|\|
| * cherry pick tidy up (#14244)Joel Challis2021-08-314-39/+6
| |
* | Move feature suspend logic out of platform specific code (#14210)Drashna Jaelre2021-08-303-179/+6
|/
* add wait_cpuclock() macro for AVR and CPU_CLOCK macro (#12755)Takeshi ISHII2021-08-242-5/+8
|
* eeprom_stm32: implement high density wear leveling (#12567)Donald Kjer2021-08-237-176/+1206
| | | | | | | | | | | | | | | * eeprom_stm32: implement wear leveling Update EECONFIG_MAGIC_NUMBER eeprom_stm32: check emulated eeprom size is large enough * eeprom_stm32: Increasing simulated EEPROM density on stm32 * Adding utility script to decode emulated eeprom * Adding unit tests * Applying qmk cformat changes * cleaned up flash mocking * Fix for stm32eeprom_parser.py checking via signature with wrong base * Fix for nk65 keyboard Co-authored-by: Ilya Zhuravlev <whatever@xyz.is> Co-authored-by: zvecr <git@zvecr.com>
* Support using a timer for wait_us() on ChibiOS-based boards (#12211)Simon Arlott2021-08-203-78/+125
| | | | | | | | | | | | | | | | | | | | | * Support using a timer for wait_us() on ChibiOS-based boards (#12198) There are spare GPT timers that can be used to get a more accurate wait_ms() time. This is required for the matrix scan unselect delay (30µs) to be shorter than the system tick rate of 100µs. This is limited to the maximum GPT duration of 65535 so values above that will automatically use the previous implementation based on the system tick. Using a specific timer means it can't be shared by another thread at the same time so when wait_us() is called from anything other than the main thread it will use the system tick implementation too. * Update tmk_core/common/chibios/wait.c * Update tmk_core/common/chibios/wait.c Co-authored-by: Joel Challis <git@zvecr.com>
* Migrate platform independent code from tmk_core -> quantum (#13673)Joel Challis2021-08-1816-4805/+0
| | | * Migrate action|keyboard|keycode|eeconfig from tmk_core -> quantum
* Begin to carve out platform/protocol API - Single main loop (#13843)Joel Challis2021-08-184-0/+85
| | | | | * Begin to carve out platform/protocol API * Fix up after rebase
* Digitizer HID interface : absolute coordinates for mouse cursor (#12851)a-chol2021-08-184-1/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add digitizer HID interface for setting the mouse cursor position at absolute screen coordinates. Tested on Pro Micro, Proton C and Blackpill. * Update docs/feature_digitizer.md Co-authored-by: Ryan <fauxpark@gmail.com> * Update tmk_core/protocol/usb_descriptor.c Co-authored-by: Ryan <fauxpark@gmail.com> * Add missing copyrights Add V-USB support * Add support for digitizer dedicated endpoint for lufa and chibios. Fix formatting issues Move digitizer_task definition to the feature's base implementation file * Run cformat on modified files * Change digitizer report usage to Digitizer instead of Pen to avoid pointer disappearing on Windows. * Update tmk_core/protocol/vusb/vusb.c Co-authored-by: Ryan <fauxpark@gmail.com> * Run cformat from docker image * Remove send_digitizer from host_driver_t and instead rely on the declaration being the interface to the implementation in each HW-specific usb implementation. * Fix build : send_digitizer shouldn't be static in vusb and add weak-linkage implementation for tests without usb implementation * Change digitizer user interface to match pointing device's * Update documentation with new API Co-authored-by: a-chol <nothing@none.com> Co-authored-by: Ryan <fauxpark@gmail.com>
* Unify behaviour of wait on AVR (#14025)Joel Challis2021-08-161-2/+20
|
* Add HOLD_ON_OTHER_KEY_PRESS option for dual-role keys (#9404)Sergey Vlasov2021-08-071-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add HOLD_ON_OTHER_KEY_PRESS option for dual-role keys Implement an additional option for dual-role keys which converts the dual-role key press into a hold action immediately when another key is pressed (this is different from the existing PERMISSIVE_HOLD option, which selects the hold action when another key is tapped (pressed and then released) while the dual-role key is pressed). The Mod-Tap keys already behave in a similar way, unless the IGNORE_MOD_TAP_INTERRUPT option is enabled (but with some additional delays); the added option makes this behavior available for all other kinds of dual-role keys. * [Docs] Update tap-hold docs for HOLD_ON_OTHER_KEY_PRESS Document the newly added HOLD_ON_OTHER_KEY_PRESS option and update the documentation for closely related options (PERMISSIVE_HOLD and IGNORE_MOD_TAP_INTERRUPT). Use Layer Tap instead of Mod Tap in examples for PERMISSIVE_HOLD and HOLD_ON_OTHER_KEY_PRESS, because the effect of using these options with Mod Tap keys is mostly invisible without IGNORE_MOD_TAP_INTERRUPT. Add comments before return statements in sample implementations of `get_ignore_mod_tap_interrupt()`, `get_hold_on_other_key_press()` and `get_permissive_hold()`. Thanks to @Erovia and @precondition for comments and suggestions to improve the documentation.
* Merge remote-tracking branch 'origin/master' into developQMK Bot2021-08-064-0/+18
|\
| * Avoid name conflicts with usb_hid Arduino code (#13870)Joel Challis2021-08-064-0/+18
| | | | | | | | | | * Avoid name conflicts with usb_hid Arduino code * Fix tests
* | Process combos earlier & overlapping combos (#8591)Pete Sevander2021-08-064-16/+68
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Combo processing improvements. Now it is possible to use ModTap and LayerTap keys as part of combos. Overlapping combos also don't trigger all the combos, just exactly the one that you press. New settings: - COMBO_MUST_HOLD_MODS - COMBO_MOD_TERM - COMBO_TERM_PER_COMBO - COMBO_MUST_HOLD_PER_COMBO - COMBO_STRICT_TIMER - COMBO_NO_TIMER * Remove the size flags from combo_t struct boolean members. This in the end actually saves space as the members are accessed so many times. The amount of operations needed to access the bits uses more memory than setting the size saves. * Fix `process_combo_key_release` not called correctly with tap-only combos * Fix not passing a pointer when NO_ACTION_TAPPING is defined. * Docs for `COMBO_ONLY_FROM_LAYER` * Update docs/feature_combo.md Co-authored-by: precondition <57645186+precondition@users.noreply.github.com> * Update quantum/process_keycode/process_combo.c Co-authored-by: precondition <57645186+precondition@users.noreply.github.com> * Add `EXTRA_SHORT_COMBOS` option. Stuff combo's `disabled` and `active` flags into `state`. Possibly can save some space. * Add more examples and clarify things with dict management system. - Simple examples now has a combo that has modifiers included. - The slightly more advanced examples now are actually more advanced instead of just `tap_code16(<modded-keycode>)`. - Added a note that `COMBO_ACTION`s are not needed anymore as you can just use custom keycodes. - Added a note that the `g/keymap_combo.h` macros use the `process_combo_event` function and that it is not usable in one's keymap afterwards. * Update docs/feature_combo.md Co-authored-by: precondition <57645186+precondition@users.noreply.github.com> * Update docs/feature_combo.md Co-authored-by: precondition <57645186+precondition@users.noreply.github.com> * Update docs/feature_combo.md Co-authored-by: precondition <57645186+precondition@users.noreply.github.com> * Update docs/feature_combo.md Co-authored-by: precondition <57645186+precondition@users.noreply.github.com> * Update docs/feature_combo.md Co-authored-by: precondition <57645186+precondition@users.noreply.github.com> * Change "the" combo action example to "email" example. * Update docs/feature_combo.md Co-authored-by: precondition <57645186+precondition@users.noreply.github.com> * Fix sneaky infinite loop with `combo_disable()` No need to call `dump_key_buffer` when disabling combos because the buffer is either being dumped if a combo-key was pressed, or the buffer is empty if a non-combo-key is pressed. * Update docs/feature_combo.md Co-authored-by: precondition <57645186+precondition@users.noreply.github.com> * Update docs/feature_combo.md Co-authored-by: precondition <57645186+precondition@users.noreply.github.com> Co-authored-by: precondition <57645186+precondition@users.noreply.github.com> Co-authored-by: Drashna Jaelre <drashna@live.com>
* | Move print/debug files to quantum (#12069)Joel Challis2021-08-039-466/+0
| | | | | | | | | | * move print/debug files to quantum * Update comments
* | Merge remote-tracking branch 'origin/master' into developQMK Bot2021-08-021-3/+5
|\|
| * flash_stm32: don't unlock flash if already unlocked (#13841)xyzz2021-08-021-3/+5
| | | | | | | | | | On stm32f4 after reboot from DFU it was observed that the flash is already unlocked. In that case, attempting to unlock it again causes a data abort.
* | __flash? (#13799)Joel Challis2021-07-311-0/+1
| |
* | Merge remote-tracking branch 'origin/master' into developQMK Bot2021-07-291-0/+18
|\|
| * Fix unit tests after recent refactor (#13765)Joel Challis2021-07-291-0/+18
| |
* | Merge remote-tracking branch 'upstream/master' into developNick Brassel2021-07-255-2/+58
|\|
| * Refactor some platform dependent logic (#13675)Joel Challis2021-07-245-6/+58
| |
* | Avoid LTO conficts on arm_atsam (#13676)Joel Challis2021-07-242-2/+2
| |
* | Merge remote-tracking branch 'origin/master' into developQMK Bot2021-07-223-0/+192
|\|
| * Implement GPIO abstraction for atsam (#13567)Joel Challis2021-07-223-0/+192
| | | | | | | | | | | | | | * Implement GPIO abstraction for atsam * Convert Drop boards to normal matrix config * Work round pin conflicts and matrix delay
* | Merge remote-tracking branch 'origin/master' into developQMK Bot2021-07-164-114/+0
|\|
| * Migrate arm_atsam print logic to use common framework (#13554)Joel Challis2021-07-164-114/+0
| |
* | [Feature] Key Overrides (#11422)Jonas Gessner2021-07-131-0/+28
| |
* | Enable g_is31_leds PROGMEM for RGB Matrix IS31FL3737 driver (#13480)Chris Cullin2021-07-121-0/+1
| |
* | core: chibios: bootloader: use integer pointers as volatile (#13450)Thomas Weißschuh2021-07-061-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | This prevents gcc from incorrectly trying to validate array bounds. ``` tmk_core/common/chibios/bootloader.c: error: '__builtin_memcpy' offset [0, 21] is out of the bounds [0, 0] [-Werror=array-bounds] 107 | __builtin_memcpy((void *) VBAT, (const void *)sys_reset_to_loader_magic, sizeof(sys_reset_to_loader_magic)); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ``` See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578#c16 Fixes #12925
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-12 12:02:31 +0000