summaryrefslogtreecommitdiffstats
path: root/platforms
Commit message (Collapse)AuthorAgeFilesLines
...
* | Update ChibiOS hardware ID (#18613)Joel Challis2022-10-051-2/+4
| |
* | onekey: Enable ADC for STM32F072 Discovery (#18592)Ryan2022-10-051-0/+1
| |
* | [Core] RP2040: use built-in integer hardware divider and optimized i64 ↵Stefan Kerkmann2022-10-041-220/+31
| | | | | | | | multiplication (#18464)
* | [Core] PWM Backlight for RP2040 (#17706)Stefan Kerkmann2022-10-045-0/+48
| |
* | [Bug] RP2040: only clear RX FIFO for serial pio driver clear (#18581)Stefan Kerkmann2022-10-041-3/+4
| |
* | [Core] Serial-protocol: always clear receive queue on main half of split ↵Stefan Kerkmann2022-10-031-8/+4
| | | | | | | | keyboard (#18419)
* | Merge remote-tracking branch 'origin/master' into developQMK Bot2022-10-033-2/+4
|\|
| * `:flash`: print bootloader (#18569)Ryan2022-10-033-2/+4
| |
* | Copy RP2040 vector table to RAM on startup (#18424)Stefan Kerkmann2022-09-221-1/+2
| | | | | | | | | | ...this reduces possible latency when invoking interrupt handlers by mitigating XIP cache misses which are not existent when running code from RAM.
* | Stabilize Half-duplex PIO split comms take 2 (#18421)Stefan Kerkmann2022-09-201-15/+2
| | | | | | | | | | | | ...by moving the actually timing critical `enter_rx_state()` and `leave_rx_state()` functions to RAM in order to not be affected by XIP cache spikes. This commit also reverts the hacky USB interrupt disabling that was done in 293c53d774
* | Add Elite-C to converters (#18309)Joel Challis2022-09-184-0/+120
| |
* | Add UART support for Kinetis boards (#18370)Ryan2022-09-172-17/+41
| | | | | | | | | | * Add UART support for Kinetis boards * Default PAL mode for GPIOV1
* | Reboot wb32 devices after flashing (#18323)Joel Challis2022-09-101-1/+2
| |
* | Add Elite-Pi converter (#18236)Danny2022-09-082-0/+45
| | | | | | Co-authored-by: Joel Challis <git@zvecr.com>
* | Prevent USB peripheral fault when restarting USB on WB32 MCUs (#18058)Joy Lee2022-09-013-0/+10
| | | | | | Co-authored-by: Joy <chang.li@westberrytech.com>
* | Merge remote-tracking branch 'origin/master' into developQMK Bot2022-09-012-11/+2
|\|
| * Remove non promicro pins from converters (#18239)Joel Challis2022-09-012-11/+2
| |
* | Move bootloader.mk to platforms (#18228)Ryan2022-08-313-0/+312
| |
* | Use a macro to compute the size of arrays at compile time (#18044)Jeff Epler2022-08-301-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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>
* | Remove deprecated USBasp and bootloadHID bootloader types (#18195)Ryan2022-08-281-2/+2
|/
* Add eeprom defaults for tinyuf2 bootloader (#18042)Joel Challis2022-08-251-4/+0
|
* Use the correct bootloader definition. (#18102)Nick Brassel2022-08-191-1/+1
|
* Add Bonsai C4 converter (#17711)David Hoelscher2022-08-182-0/+44
|
* Fix GD32VF103 WS2812 PWM driver (#18067)Stefan Kerkmann2022-08-151-0/+2
| | | ...by adding the missing STM32 DMA defines.
* Partially revert some WB32 specific changes (#18038)Joel Challis2022-08-142-23/+10
|
* [Controller] Added board config for custom controller STeMCell (#16287)Mega Mind2022-08-148-0/+382
| | | | | Co-authored-by: Mariappan Ramasamy <947300+Mariappan@users.noreply.github.com> Co-authored-by: Mariappan Ramasamy <maari@basis-ai.com> Co-authored-by: Sadek Baroudi <sadekbaroudi@gmail.com>
* Fix buffer size for WS2812 PWM driver (#17046)yiancar2022-08-131-4/+48
| | | | | Co-authored-by: Drashna Jaelre <drashna@live.com> Co-authored-by: Sergey Vlasov <sigprof@gmail.com> Co-authored-by: yiancar <yiancar@gmail.com>
* Added ws2812_pwm support for WB32 MCU. (#17142)Joy Lee2022-08-131-4/+23
| | | Co-authored-by: Joy <chang.li@westberrytech.com>
* Added ws2812_spi support for WB32 MCU (#17143)Joy Lee2022-08-132-2/+13
| | | Co-authored-by: Joy <chang.li@westberrytech.com>
* Improve avr wait_us() (#16879)Takeshi ISHII2022-08-141-9/+29
|
* Add Bit-C PRO converter (#17827)Jay Greco2022-08-132-0/+51
|
* Added implementation of WB32 MCU wear_leveling_efl. (#17579)Joy Lee2022-08-131-0/+2
|
* Add minimal STM32F103C6 support (#17853)Sergey Vlasov2022-08-115-1/+28
| | | | | | | | | | | | | | | | | | | | | | | | Unfortunately, the crippled versions of “Bluepill” boards with STM32F103C6xx chips instead of STM32F103C8xx are now sold all over the place, sometimes advertised in a confusing way to make the difference not noticeable until too late. Add minimal support for these MCUs in the common “Bluepill with stm32duino” configuration, so that it could be possible to make something useful from those boards (although fitting QMK into the available 24 KiB of flash may be rather hard). (In fact, I'm not sure whether the “STM32” part of the chip name is actually correct for those boards of uncertain origin, so the onekey board name is `bluepill_f103c6`; another reason for that name is to match the existing `blackpill_f401` and `blackpill_f411`.) The EEPROM emulation support is not included on purpose, because enabling it without having a working firmware size check would be irresponsible with such flash size (the chance that someone would build a firmware where the EEPROM backing store ends up overlapping some firmware code is really high). Other than that, enabling the EEPROM emulation code is mostly trivial (the `wear_leveling` driver with the `embedded_flash` backing store even works without any custom configuration, although its code is significantly larger than the `vendor` driver, which may also be important for such flash size).
* Fix issue with #17904. (#17905)Nick Brassel2022-08-041-1/+1
|
* Fixup compilation of printf-like functions with uint32_t args. (#17904)Nick Brassel2022-08-041-10/+10
|
* [Core] `STM32_USB_USE_OTG1` => `USB_ENDPOINTS_ARE_REORDERABLE` (#17647)Nick Brassel2022-08-041-0/+2
|
* Remove legacy AVR ssd1306 driver (#17864)Joel Challis2022-07-312-416/+0
|
* [Core] RP2040 disable PIO IRQs on serial timeout (#17839)Stefan Kerkmann2022-07-291-0/+2
|
* ChibiOS: use correct status codes in i2c_master.c (#17808)Stefan Kerkmann2022-07-281-2/+2
| | | | msg_t is MSG_OK in the success case and either MSG_RESET or MSG_TIMEOUT in case of errors. So actually use them in the comparison.
* Chibios: Stop I2C peripheral on transaction error (#17798)Stefan Kerkmann2022-07-261-15/+24
| | | | | | | | | | | | | | From the ChibiOS HAL I2C driver pages: After a timeout the driver must be stopped and restarted because the bus is in an uncertain state. This commit does that stopping explicitly on any error that occurred, not only timeouts. As all the i2c functions restart the peripheral if necessary it is safe to do so. Co-authored-by: Dasky <32983009+daskygit@users.noreply.github.com> Co-authored-by: Dasky <32983009+daskygit@users.noreply.github.com>
* Add Blok 2040 conversion (#17603)Albert Y2022-07-212-0/+45
|
* Use Pro Micro pinout for SDA/SCL (#17595)Albert Y2022-07-201-2/+2
|
* Post-bootloader EFL/SPI fixes. (#17661)Nick Brassel2022-07-142-2/+4
| | | | | | | * Fixup read address for EFL driver. * Fixup sequencing of SPI. * Lock during init of EFL backing store.
* Allow MCU-specific overrides for SPI flags. (#17650)Nick Brassel2022-07-132-3/+18
|
* Include stdint.h in avr/i2c_master.h (#17639)jack2022-07-121-0/+2
|
* [Fix] Make ChibiOS `_wait.h` independent of `quantum.h` (#17645)Stefan Kerkmann2022-07-121-0/+1
|
* [Core] Use polled waiting on ChibiOS platforms that support it (#17607)Stefan Kerkmann2022-07-115-5/+22
| | | | | | | | | | | | | | | | | | | | | | | | * 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
* Stabilize Half-duplex PIO split comms (#17612)Stefan Kerkmann2022-07-111-3/+17
|
* Update PM2040 I2C pins (#17578)Albert Y2022-07-071-2/+2
|
* [Core] Update mpaland/printf to eyalroz/printf fork (#16163)Stefan Kerkmann2022-07-073-1/+4
| | | | | | | | mpaland printf implementation was abandoned in ~2019 and the fork by eyalroz is now regarded to be the goto replacement of it. So this commit incoporates the changes needed to use this fork in QMK. Note that pointer ptrdiff_t is always supported since commit 51c90f93a97fdaef895783ecbe24569be0db7cb8