summaryrefslogtreecommitdiffstats
path: root/drivers
Commit message (Collapse)AuthorAgeFilesLines
...
* format code according to conventions [skip ci]QMK Bot2020-02-132-772/+223
|
* Fix RESET keycode on some STM32F072 keyboards (#8134)Joel Challis2020-02-135-0/+1747
| | | | | | | | | | | | | | * Add f072 board files with 'enter_bootloader_mode_if_requested' support * rename default f072 board file to GENERIC_STM32_F072XB * Remove board files * Add bootloader def * Update generic f072 board paths * Revert wrong deletion
* Fix out of bound OLED font access (#8145)Ted M Lin2020-02-112-3/+5
| | | | | | | | | | | | | | | * Fix out of bound OLED font access The default font is 1344 bytes, or a total of 224 glyphs (each 6-bytes wide). OLED_FONT_END defaults to 224, which if used will then index off the end of the font array. So either the documentation or code is wrong. Instead of figuring out the rewording of the documentation, just change the OLED_FONT_END default value to 223, to match the documentation and code. * Add static assert to check array size Build bomb if the font array size doesn't match to the defines.
* Add thread safety around i2c_master for ChibiOS/ARM.Nick Brassel2020-02-011-12/+51
|
* Refactor stm32duino f103 keyboards to use new central board config files (#7706)Joel Challis2020-01-273-0/+227
|\ | | | | | | | | | | | | | | | | | | * Create central board for bluepill * Remove duplicate board files * Refactor to use new central board config files * Fix cannonkeys f103 boards
| * Create central board for bluepillzvecr2020-01-263-0/+227
| |
* | Migrate common ld scripts to common location (#7887)Joel Challis2020-01-273-0/+294
|/ | | | | | | | * Migrate common ld scripts to common location * Remove duplicate ld scripts * Update build to look at common ld location
* Update split serial code to use driver pattern (#7990)Joel Challis2020-01-242-0/+570
| | | | | | * Move avr serial code to drivers * Update src+= serial.c to driver pattern
* format code according to conventions [skip ci]QMK Bot2020-01-241-1/+1
|
* Add customisable EEPROM driver selection (#7274)Nick Brassel2020-01-247-0/+453
| | | | | | | | | - uprintf -> dprintf - Fix atsam "vendor" eeprom. - Bump Kinetis K20x to 64 bytes, too. - Rollback Kinetis to 32 bytes as partitioning can only be done once. Add warning about changing the value. - Change RAM-backed "fake" EEPROM implementations to match eeconfig's current usage. - Add 24LC128 by request.
* Run clang-format manually to fix recently changed files (#7934)Joel Challis2020-01-191-1/+1
| | | | | | | | * Run clang-format manually to fix recently changed files * Run clang-format manually to fix recently changed files - revert template files * Run clang-format manually to fix recently changed files - format off for ascii_to_keycode_lut
* SPI DMA based RGB Underglow for STM32 (#7674)Joel Challis2019-12-311-1/+90
| | | | | | | | | | * Initial stash of ws2812 spi driver * Update comment, add sync backup plan * Add testing notes to spi ws2812 driver * Align RGBW error messages
* Clean up ISSI driver includes (#7734)fauxpark2019-12-2910-95/+25
| | | | | | * Clean up ISSI driver includes * Missed an endif
* Add backwards compatibility for oled_write_raw_P on ARMzvecr2019-12-241-0/+2
|
* Completely remove i2c_transmit_receive function (#7686)Drashna Jaelre2019-12-222-10/+2
| | | | | | | | | | * Add i2c_transmit_receive function This function is listed in the ARM header file, but doesn't actually exist. * Remove i2c_transmit_receive function * Update DRV2605L read function to use i2c_readReg on both arm and avr
* Add central location for ChibiOS defines (#7542)Joel Challis2019-12-212-20/+11
| | | | | | | | | | * Add central location for chibios defines * Add central location for chibios defines - actually add files this time.... * Add Copyright header * Update include order to resolve i2cv1 build errors
* fixed I2C driver support for stm32f4 (#7526)yulei2019-12-122-10/+16
| | | | | | | | * correct i2c driver for stm32f4 * update pin mode definitions * update macro definition
* Enable bitbang ws2812 for f4 (#7571)Joel Challis2019-12-081-1/+1
|
* Improve support and docs for ADC driver (#7191)fauxpark2019-12-082-39/+108
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Improve support and docs for ADC driver * Comment ADC channels * Move to Makers and Modders section, and fix usage instructions * Flesh out intro * Superscript 328P note * Fix pin_to_mux LUT * Support USB64/1287 as well * analogReadPin() defaults to 0V mux on invalid pin * Update pinToMux() function documentation * Dot * Accept (some of) the `qmk cformat` changes * Do clang-format properly * More wording tweaks * Link to encoder docs
* Increase matrix scanning speed on xd84 (#7517)Joel Challis2019-12-032-0/+19
| | | | | | * Increase matrix scanning speed * Fix func name in failure output
* IS31FL3733 Dirty page fix (#7079)yiancar2019-11-252-20/+34
| | | | | | | | | | | | | | | | | | | | | | | | | * IS31FL3733 Dirty page fix Function IS31FL3733_update_led_control_registers was never setting update register to false. As a result the led on/off page was being written every transaction even when it was not modified. This is ineficient and causes lots of bandwidth use. -> Fix the IS31FL3733_update_led_control_registers. -> After testing it was evident that failed I2C transactions could corrupt the Led on/off register. -> Update IS31FL3733_write_pwm_buffer and IS31FL3733_write_register functions to return 0 upon succesful tranmission and 1 if any of the transmitions within the function fail. -> Modify IS31FL3733_update_pwm_buffers function so if any of the IS31FL3733_write_pwm_buffer transuction fails, the g_led_control_registers_update_required register is set to true forcing a rewrite of the led on/off register in case it was corrupted. * Minor comment update * Upsie:) * Update is31fl3733.c * Return fix * more return fix * type change * more boolian logic reversal:)
* Run clang-format manually to fix recently changed fileszvecr2019-11-173-59/+54
|
* Improvements to Solenoid feature (#7369)Drashna Jaelre2019-11-151-5/+1
| | | | | | | | | | * Error out when Solenid pin is not defined Instead of defaulting to a (literally) random pin, error out instead. Because this pin may be used, or because that pin may not be exposed, or may not exist. * Remove 'SOLENOID_ACTIVE' setting since it's not used * Update documentation
* Move Ergodox EZ RGB Light code to custom driver (#7309)Drashna Jaelre2019-11-141-127/+2
| | | | | | | | | | | | | | | | | | | * Move Ergodox EZ RGB code to custom driver Also implements full addressing of Ergodox EZ's LED Strip, as written by seebs Co-authored-by: Seebs <seebs@seebs.net> * Make Clipping range accessible for custom drivers * Remove RGBW_BB_TWI from driver and docs * Revert changes to clipping range support * Use just rgblight_set instead of full custom driver * Convert to i2c_master commands * Rename rgblight driver and clean up includes
* Unify RGB and RGBW commands (#7297)Drashna Jaelre2019-11-095-35/+16
| | | | | | | | | | | | | | | | | | | | | | * Fix unicode in comments Co-Authored-By: fauxpark <fauxpark@gmail.com> * Remove separate RGBW implementation for a unified function * Set White to 0 in RGBW LEDs This is just to get this working, later, proper brightness can be handled elsewhere. * Use us instead of nanoseconds(?) since it renders correctly on web * Remove RGBW function from arm/ws2812.h * Remove RGBW function from arm/ws2812.c * Formatting changes * Add doc info
* ARM - ws2812 bitbang (#7173)Joel Challis2019-11-072-1/+117
| | | | | | | | | | | | | | | | | | | | * Initial ARM bitbang ws2812 driver * Unify chibios platform to run rgblight_task * Remove 'avr only' comments from ws2812 docs * Remove 'avr only' comments from ws2812 docs * Unify chibios platform to run rgblight_task - review comments * Remove debug flags from keymap * Add comments from review * Add defines for STM32L0XX * Attempt to get arm ws2812 working on multiple gcc versions
* Fix typo in ARM I2C copyright header (#7264)fauxpark2019-11-041-2/+2
|
* Adds raw write functions to the OLED driver (#7237)Thomas Baart2019-11-032-2/+25
| | | | | | * Added oled_write_raw and oled_write_raw_P functions to the OLED driver * Added oled_write_raw method calls to feature_oled_driver.md
* Correct ARM STM32 I2C frequency. (#7080)yiancar2019-10-311-5/+5
| | | | | | | | It was beleaved that this setting result in a 400Khz I2C bus. This was incorrect, actual frequency measure with a logic analyzer was around 150Khz. This is derived from the excel sheet linked in the .h file. Also confirmed with the ST IDE.
* Refactor ps2avrgb i2c ws2812 to core (#7183)Joel Challis2019-10-294-0/+34
| | | | | | | | | | | | | | | | | | | | * Refactor ps2avrgb i2c ws2812 to core * Refactor jj40 to use ws2812 i2c driver * Refactor ps2avrgb template to use ws2812 i2c driver * Add ws2812 stub files * clang-format and driver config * Add ws2812 driver docs * Fix default config values * Update tmk_core/protocol/vusb/main.c Co-Authored-By: Drashna Jaelre <drashna@live.com>
* Reduce duplication for ARM/AVR ws2812 RGB Matrix driver (#7180)Joel Challis2019-10-292-57/+11
| | | | | | * Reduce duplication for ARM/AVR ws2812 rgb_matrix driver * Reduce duplication for ARM/AVR ws2812 rgb_matrix driver - Fix setled_all use of r,g,b
* Remove i2c logic for STM32F103xB in favour of USE_I2CV1 (#6926)Joel Challis2019-10-121-12/+2
| | | | | | * Remove i2c logic for STM32F103xB in favour of USE_I2CV1 * Remove i2c logic for STM32F103xB in favour of USE_I2CV1
* [Keyboard] RGB updates on NK65 and HS60 (#6795)yiancar2019-10-081-1/+2
| | | | | | | | * RGB update commit * Convert caps lock indicator check to IS_LED_ON * ISSI3733 minor change
* [Keyboard] Added support for ErgoDox with STM32 Microcontroller (#5398)Yaotian Feng2019-09-251-3/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Began Work On STM32 Ergodox Changes to be committed: new file: keyboards/ergodox_stm32/config.h new file: keyboards/ergodox_stm32/rules.mk * test * Now it compile. Not linking thou * Screw this Linker. It links now! * Blinkly Keyboard * bootloader test code * Working on matrix / i2c stuff * Progress (LED Blink) * Progress on MCP_23017 Status Flag * [WIP] * update * Works! Remeber to change back the bootloader address when the new bootloadrer is ready. * Time to go debug the i2c * Finally, it now works with PCB Rev 1.0.2 * updated for rev.2 pcb * minor compilation fix * Why when debugger is enabled then everything works. * Remeber to call init functions. * Update arm i2c driver to support STM32F103 series device. * fix include once header. Replaced with #pragma once. * complication test
* DRV2605L Continuous Haptic Feedback Support (#6461)MechMerlin2019-09-194-6/+91
| | | | | | | | | | | | | | | | | | | | | | | | * provide means to turn on RTP mode and set the amplitude * new keycode HPT_CONT to turn RTP off/on * introduce new keycodes HPT_CONI, and HPT_COND for Haptic Continuous Increase and Decrease * support for continuous mode amplitude increase and decrease * code cleanup * update docs to reference new keycodes and functionality * don't touch the keymaps * add function prototypes * add proper guards * cleanup guards * remove extra reserved
* Fix battery level code in adafruit_ble.cpp (#6648)bwhelm2019-09-041-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Fix battery level code in adafruit_ble.cpp The code in tsk_core/protocol/lufa/adafluit_ble.cpp that polls the battery level for the Adafruit feather BLE controller reads the regulated voltage, not the raw voltage coming from the battery. To do that, the Adafruit Feather docs say you should read from pin A9: https://learn.adafruit.com/adafruit-feather-32u4-basic-proto/power-management#measuring-battery-4-9. (See also https://learn.adafruit.com/adafruit-feather-32u4-bluefruit-le/pinouts#logic-pins-2-9.) I'm not sure why, but analogRead(9); doesn't read the correct pin. Checking all available analog pins experimentally, it turns out that analogRead(7); returns the correct value. So the code above should read: state.vbat = analogRead(7); * Update tmk_core/protocol/lufa/adafruit_ble.cpp Co-Authored-By: Drashna Jaelre <drashna@live.com> * Remove old comment * Fix linking error * Remove `#ifdef` around `#include analog.h`. * Really fix linking error
* Removed prescaler define from avr i2c, as it was impossible to use (#6617)Mikkel Jeppesen2019-08-301-2/+2
|
* Fix Redefinition of OLED_TIMEOUT (#6628)Drashna Jaelre2019-08-301-1/+0
|
* clang-format changesskullY2019-08-3057-7001/+4882
|
* Added OLED Display autoscroll during periods of OLED data inactivity (#6546)XScorpion22019-08-252-6/+42
| | | | | | | | * Added OLED Display autoscroll during periods of OLED data inactivity. * Fixing compile errors * Feedback from review
* Relocate pca9555 driver to core (#6563)Joel Challis2019-08-222-0/+133
| | | | | | | | * Move pca9555 files to central location * Get pca9555 boards compiling * Slight alignment of rules.mk
* (OLED) Added support for CR (#6399)XScorpion22019-07-271-1/+6
| | | | | Currently OLED Dirver only supports LF (\n) character in a string to clear out the rest of the current line and advance to the next line for writing. This PR adds support for CR (\r) character as well to advance to the next line, however not clear out the rest of the current line. This is extremely useful when you want to display a multi-line logo using a single array without wiping out exiting lines and flagging the OLED as dirty unnecessarily.
* Refactoring wilba.tech PCBs, updating Rama Works U80-A (#6272)Wilba2019-07-212-21/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Added WT65-B, WT75-B, minor fixes * Update keyboards/wilba_tech/wt65_b/config.h Co-Authored-By: Drashna Jaelre <drashna@live.com> * Update keyboards/wilba_tech/wt65_b/readme.md Co-Authored-By: fauxpark <fauxpark@gmail.com> * Update keyboards/wilba_tech/wt75_b/config.h Co-Authored-By: Drashna Jaelre <drashna@live.com> * Change DEBOUNCING_DELAY to DEBOUNCE * Change DEBOUNCING_DELAY to DEBOUNCE * Move Zeal60/Zeal65 files to keyboards/wilba_tech * Change DEBOUNCING_DELAY to DEBOUNCE * Refactoring zeal60 code to wilba_tech * Moved Rama Works PCBs to wilba_tech * Rename Rama Works files * Cleanup info.json * Cleanup readme.md * Cleanup USB device strings * U80-A RGB matrix, IS31FL3731 driver changes * Fixed #include from keyboards/zeal60
* Align ARM i2c_readReg with AVR (#6314)Joel Challis2019-07-162-3/+3
| | | | | | * Align arm i2c_readReg with avr * Align arm i2c_readReg with avr - fix cannonkeys
* Add ARM I2Cv1 support to i2c_master (#6262)Joel Challis2019-07-162-23/+52
| | | | | | * Add ARM I2Cv1 support to i2c_master * Add I2Cv1 docs
* Add GPL3 header to avr i2c files (#6332)Drashna Jaelre2019-07-154-2/+62
| | | | | | | | * Add GPL3 header to avr i2c files * Add for i2c_slave as well * Fix formatting of license header
* Use QUANTUM_LIB_SRC for i2c_master.c inclusion (#5617)Drashna Jaelre2019-07-091-3/+1
| | | Using QUANTUM_LIB_SRC prevents the warning when multiple sources add the i2c_master.c file. Boards such as the Ergodox EZ Glow see this warning every time they compile because the board uses the file in general, and because the RGB LED Matrix requires it, as well.
* Add SH1106 OLED support (#5787)Michael F. Lamb2019-06-112-4/+41
| | | | | | | | | | | | | | | | | * modify oled_driver to support SH1106 also: - improve mechanism to specify which OLED IC we use - comment calc_bounds() - give OLED_COLUMN_OFFSET a default value - inline comment re: OLED MEMORY_MODE and SH1106 - update docs/feature_oled_driver.h for SH1106 support and related changes - docs: OLED: note we have tested SSD1306 on ARM boards (per @XScorpion2) - define out MEMORY_MODE when using SH1106 OLED driver * document that SSD1306 128x64 on AVR works Per @XScorpion2: https://github.com/qmk/qmk_firmware/pull/5787#discussion_r291837842
* Fixing OLED Driver for 128x64 displays (#6085)XScorpion22019-06-072-4/+49
|
* Moving rgb typedefs into a single location (#5978)XScorpion22019-06-042-2/+2
| | | | | Because someone named the define poorly Using full relative path as handwired/promethium has a color.h file
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 20:24:01 +0000