summaryrefslogtreecommitdiffstats
path: root/keyboards/handwired/onekey/keymaps
Commit message (Collapse)AuthorAgeFilesLines
* rgblight: driver selection cleanups (#21558)Ryan2023-08-151-1/+1
|
* OLED: driver naming cleanups (#21710)Ryan2023-08-151-1/+0
|
* haptic: naming cleanups (#21551)Ryan2023-07-211-1/+1
|
* onekey: Fix console output on AVR (#19930)Sergey Vlasov2023-04-032-2/+2
|
* Remove deprecated Quantum keycodes (#19712)Ryan2023-01-291-1/+1
|
* Fix functions with empty params (#19647)Ryan2023-01-202-2/+2
| | | | | * Fix functions with empty params * Found a bunch more
* Merge remote-tracking branch 'origin/master' into developQMK Bot2023-01-191-0/+2
|\
| * Fixup ChibiOS header inclusion search ordering. (#19623)Nick Brassel2023-01-191-0/+2
| | | | | | | | | | | | | | | | * Add STM32F446-Nucleo onekey. * Fixup onekey build for F446, all keymaps. * Fixup board inclusion search ordering.
* | Tap Dance: remove `qk_` prefix (#19313)Ryan2022-12-142-5/+5
| |
* | [Core] Quantum Painter - LVGL Integration (#18499)jpe2302022-12-135-0/+89
|/ | | Co-authored-by: Nick Brassel <nick@tzarc.org>
* Fixup EFL and F4's sector selection. (#19221)Nick Brassel2022-12-023-0/+72
|
* Joystick feature improvements (#19052)Ryan2022-11-272-2/+2
|
* Merge remote-tracking branch 'origin/master' into developQMK Bot2022-11-184-0/+12
|\
| * Disable onekey console by default (#19104)Joel Challis2022-11-184-0/+12
| |
* | Digitizer feature improvements (#19034)Ryan2022-11-121-26/+46
| |
* | Remove rgblight_list.h (#18878)Ryan2022-10-272-2/+2
| | | | | | | | | | | | | | | | | | | | | | * Remove rgblight_list defines with no usage * Remove rgblight_setrgb_*[_at] defines * Remove rgblight_sethsv_* defines * Remove rgblight_sethsv_noeeprom_* defines * Delete rgblight_list.h and remove all references
* | Normalise Joystick and Programmable Button keycodes (#18832)Ryan2022-10-241-1/+1
| |
* | Remove legacy EEPROM clear keycodes (#18782)Ryan2022-10-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | * `EEP_RST` -> `EE_CLR`, default-ish keymaps * `EEP_RST` -> `EE_CLR`, user keymaps * `EEP_RST` -> `EE_CLR`, community layouts * `EEP_RST` -> `EE_CLR`, userspace * `EEP_RST` -> `EE_CLR`, docs & core
* | Remove RGBLIGHT_ANIMATION and clean up effect defines for G-K (#18726)Drashna Jaelre2022-10-152-2/+20
| |
* | Merge remote-tracking branch 'origin/master' into developQMK Bot2022-10-011-3/+2
|\|
| * onekey: fix quine keymap (#18555)Ryan2022-10-011-3/+2
| |
* | Merge remote-tracking branch 'upstream/master' into developfauxpark2022-09-301-2/+2
|\|
| * Onekey: migrate some stuff to data driven (#18502)Ryan2022-09-301-2/+2
| |
* | Further refactoring of joystick feature (#18437)Ryan2022-09-271-5/+1
| |
* | Use a macro to compute the size of arrays at compile time (#18044)Jeff Epler2022-08-301-2/+2
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add ARRAY_SIZE and CEILING utility macros * Apply a coccinelle patch to use ARRAY_SIZE * fix up some straggling items * Fix 'make test:secure' * Enhance ARRAY_SIZE macro to reject acting on pointers The previous definition would not produce a diagnostic for ``` int *p; size_t num_elem = ARRAY_SIZE(p) ``` but the new one will. * explicitly get definition of ARRAY_SIZE * Convert to ARRAY_SIZE when const is involved The following spatch finds additional instances where the array is const and the division is by the size of the type, not the size of the first element: ``` @ rule5a using "empty.iso" @ type T; const T[] E; @@ - (sizeof(E)/sizeof(T)) + ARRAY_SIZE(E) @ rule6a using "empty.iso" @ type T; const T[] E; @@ - sizeof(E)/sizeof(T) + ARRAY_SIZE(E) ``` * New instances of ARRAY_SIZE added since initial spatch run * Use `ARRAY_SIZE` in docs (found by grep) * Manually use ARRAY_SIZE hs_set is expected to be the same size as uint16_t, though it's made of two 8-bit integers * Just like char, sizeof(uint8_t) is guaranteed to be 1 This is at least true on any plausible system where qmk is actually used. Per my understanding it's universally true, assuming that uint8_t exists: https://stackoverflow.com/questions/48655310/can-i-assume-that-sizeofuint8-t-1 * Run qmk-format on core C files touched in this branch Co-authored-by: Stefan Kerkmann <karlk90@pm.me>
* RESET -> QK_BOOT user keymaps (#17940)Joel Challis2022-08-211-1/+1
|
* [Core] Use polled waiting on ChibiOS platforms that support it (#17607)Stefan Kerkmann2022-07-112-0/+59
| | | | | | | | | | | | | | | | | | | | | | | | * Use polled waiting on platforms that support it Due to context switching overhead waiting a very short amount of time on a sleeping thread is often not accurate and in fact not usable for timing critical usage i.e. in a driver. Thus we use polled waiting for ranges in the us range on platforms that support it instead. The fallback is the thread sleeping mechanism. This includes: * ARM platforms with CYCCNT register (ARMv7, ARMv8) this is incremented at CPU clock frequency * GD32VF103 RISC-V port with CSR_MCYCLE register this is incremented at CPU clock frequency * RP2040 ARMv6 port which uses the integrated timer peripheral which is incremented with a fixed 1MHz frequency * Use wait_us() instead of chSysPolledDelayX ...as it is powered by busy waiting now. * Add chibios waiting methods test bench
* [Feature] Add support for multiple switchs/solenoids to Haptic Feedback ↵Drashna Jaelre2022-05-152-0/+13
| | | | engine (#15657)
* [Core] Add Reboot keycode to core (#15990)Drashna Jaelre2022-05-141-0/+5
|
* Expose API for hardware unique ID (#16869)Joel Challis2022-04-181-0/+28
|
* Joystick feature updates (#16732)Ryan2022-03-261-2/+0
| | | | | | | * Joystick feature updates * Move new functions to joystick.h * Docs
* [Keymap] Fix onekey oled keymap (#15751)Drashna Jaelre2022-01-051-1/+1
|
* [Core] Change OLED task function to be boolean (#14864)Drashna Jaelre2021-11-021-1/+2
| | | | | | | | | | | | | * [Core] Add kb level callbacks to OLED driver * Update keyboards and keymaps * Update docs * Update userspace configs * Add fix for my keymap ... * update lefty
* [Core] Add support for RISC-V builds and GD32VF103 MCU (#12508)Stefan Kerkmann2021-10-181-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | * 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
* Remove bootloader listings from rules.mk (#14330)Ryan2021-09-101-1/+1
|
* Bugfix for Joystick and JSON schema (#14295)Ryan2021-09-091-1/+1
|
* [Core] Refactor OLED to allow easy addition of other types (#13454)Xelus222021-08-241-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * add docs * core changes * update keyboards to new OLED * updated users to new OLED * update layouts to new OLED * fixup docs * drashna's suggestion * fix up docs * new keyboards with oled * core split changes * remaining keyboard files * Fix The Helix keyboards oled options * reflect develop Co-authored-by: Drashna Jaelre <drashna@live.com> Co-authored-by: mtei <2170248+mtei@users.noreply.github.com>
* Digitizer HID interface : absolute coordinates for mouse cursor (#12851)a-chol2021-08-182-0/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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>
* Fix onekey console keymap (#13797)Ryan2021-07-301-1/+1
|
* Onekey cleanup (#13786)Ryan2021-07-301-0/+20
|
* Cleanup junk characters, part 1 (#13282)Ryan2021-06-212-2/+2
|
* Onekey keymap: quine (#10732)ridingqwerty2021-02-282-0/+61
|
* Merge remote-tracking branch 'origin/master' into developZach White2021-01-052-32/+0
|\
| * Migrate python tests away from onekey (#11367)Joel Challis2021-01-052-32/+0
| | | | | | | | | | | | | | * Migrate python tests away from onekey * Add stub files to stop lint complaints * Make all the pytest keymaps compile
* | Rewrite APA102 support (#10894)Aldehir Rojas2020-12-303-0/+21
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Rewrite APA102 support The APA102 source was broken by commit 16a15c1cfcbfd0feb2c2cf1383676747e2f97d73 as it did not include the quantum header. This commit addresses that, as well as other issues with transferring bytes over the SPI interface, i.e. it was not setting the clock pin back to low after sending a bit. The deviation when sending the end frame is kept, but updated to the latest from the referenced project. Finally, these changes expose the global LED brightness parameter of the APA102. Brightness values are configurable through `APA102_DEFAULT_BRIGHTNESS` and `APA102_MAX_BRIGHTNESS`. * Fix typo in led brightness extern * Move driver out of AVR directory and add delay for ARM * Experimental APA102 support on AVR and ARM Co-authored-by: Alde Rojas <hello@alde.io> * Refactor apa102_send_byte() calls to a loop * Implement io_wait function for ARM * Move APA102 drivers to own directory, fix copyright notice * Add APA102 keymap to handwired/onekey * Simplify RGBLIGHT_ENABLE/DRIVER option handling Co-authored-by: Mikkel Jeppesen <2756925+Duckle29@users.noreply.github.com>
* Add brightness level API to OLED driver (#10772)Ryan2020-10-291-0/+6
| | | | | * Add brightness level API to OLED driver * Set default brightness to 255
* [CLI] Add c2json (#8817)Erovia2020-10-061-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Basic keymap parsing finally works * Add 'keymap.json' creation to the qmk.keymap module * Add tests and fix formatting * Fix/exclude flake8 errors * Convert keymap.c to valid keymap.json * Fix some errors * Add tests * Finalize keymap.json creation, add json template * Add docs * Move pygments to the standard requirements * Add support for nameless layers, fix tests * Fix things after rebase * Add missing 'keymap' value. * Fix missing layer numbers from advanced keycodes Buckwich noticed that if the advanced keycode / layer toggling key contains a number, it goes missing. Now we properly handle them. Thx for noticing! * Apply suggestions from code review * fixup tests Co-authored-by: Zach White <skullydazed@drpepper.org> Co-authored-by: skullY <skullydazed@gmail.com>
* [Keymap] Add onekey keymap for OLED testing (#10380)Sergey Vlasov2020-10-043-0/+477
| | | | | * Add onekey keymap for OLED testing * Add license header
* format code according to conventions [skip ci]QMK Bot2020-08-292-2/+2
|
* Allow joysticks to be used without analog pins (#10169)Zach White2020-08-291-1/+1
| | | | | * Allow joysticks to be used without analog pins * change how analog/digital joysticks are specified
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-21 14:10:49 +0000