summaryrefslogtreecommitdiffstats
path: root/drivers/sensors
Commit message (Collapse)AuthorAgeFilesLines
* drivers: remove direct `quantum.h` includes (#21473)Ryan2023-07-091-1/+1
|
* Added PMW3320 driver (#19543)Vladislav Marchenko2023-04-032-0/+311
|
* Remove usages of config_common.h from config.h files. (#19714)Nick Brassel2023-01-311-0/+1
|
* Fix functions with empty params (#19647)Ryan2023-01-202-2/+2
| | | | | * Fix functions with empty params * Found a bunch more
* Cleanup pmw3389.c (#19301)Alabastard-642022-12-121-2/+0
|
* Add `*_RIGHT` configuration for PMW33XX driver (#19243)Pablo Martínez2022-12-103-5/+21
|
* Fix cirque tap from secondary side (#18351)Dasky2022-09-141-8/+0
|
* 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>
* [Core] Introduce pointing device specific debug messages (#17663)Stefan Kerkmann2022-08-296-44/+19
|
* Create generic Pointing Device Pin defines (#17776)Drashna Jaelre2022-08-125-8/+42
|
* Fix POINTING_DEVICE_GESTURES_SCROLL_ENABLE typo (#17850)Daniel Kao2022-07-311-2/+2
| | | | | | | | * Fix typo for POINTING_DEVICE_GESTURES_SCROLL_ENABLE Follow the name written in documentation which follows POINTING_DEVICE_GESTURES_CURSOR_GLIDE_ENABLE * Reword the blurb about POINTING_DEVICE_GESTURES_CURSOR_GLIDE_ENABLE in docs
* Implement relative mode for Cirque trackpad (#17760)Drzony2022-07-295-38/+115
|
* Cirque circular scroll: Support POINTING_DEVICE_COMBINED (#17654)Daniel Kao2022-07-251-12/+17
|
* Add support for PAW3204 Optical Sensor (#17669)Drashna Jaelre2022-07-192-0/+240
| | | | Co-authored-by: gompa <gompa@h-bomb.nl> Co-authored-by: Stefan Kerkmann <karlk90@pm.me>
* Use correct angle tune range of +/-127 on PMW33XX (#17708)Stefan Kerkmann2022-07-172-3/+3
| | | | | ...partially reverts 580bcff4f65a3a9ee301de0fd036de7b610c7ee2 as the datasheet doesn't claim that the angle tuning as limited to +/- 30 degrees.
* Use correct angle tune range of +/-30 on PMW33XX (#17693)Stefan Kerkmann2022-07-162-1/+7
| | | | | Co-authored-by: Daniel Kao <daniel.m.kao@gmail.com> Co-authored-by: Daniel Kao <daniel.m.kao@gmail.com>
* [Core] PMW33XX drivers overhaul (#17613)Stefan Kerkmann2022-07-148-1294/+1080
| | | | | | | | | | | | | | | | | | | | | | | | | | | | * PMW33XX drivers overhaul This combines the PMW3389 and PM3360 drivers as they only differ in the firmware blobs and CPI get and set functions. The following changes have been made: * PMW3389 now gets the same multi-sensor feature that is already available on the PMW3360. * Introduced a shared pmw33xx_report_t struct is now directly readable via SPI transactions instead of individual byte-sized reads, saving multiple copies and bitshift operations. * pmw33(89/60)_get_report functions had unreachable branches in their motion detection logic these have been simplied as much as possible. * The fast firmware upload option has been removed as this becomes obsolete by the newly introduced polled waiting functions for ChibiOS polled waiting * PMW33(60/89)_SPI_LSBFIRST and PMW33(60/89)_SPI_MODE config options have been removed as they don't need to be configurable. * All PMW3389 and PMW3360 defines have been unified to a PMW33XX prefix to reduce code duplication and make the defines interchangeable * Adjust keyboards to PMW33XX naming scheme
* Fix compilation issue with Cirque Guestures file (#17656)Drashna Jaelre2022-07-131-0/+1
|
* Cirque trackpad features: circular scroll, inertial cursor (#17482)Daniel Kao2022-07-125-102/+841
|
* improvements for Cirque Pinnacle trackpads (#17091)Thomas Kriechbaumer2022-06-254-49/+109
|
* Cirque Attenuation Setting (#17342)Kyle McCreery2022-06-221-1/+6
|
* Fixup Pimoroni trackball code (#17335)jack2022-06-092-14/+0
|
* Merge remote-tracking branch 'origin/master' into developQMK Bot2022-05-131-4/+5
|\
| * [Bug] Updated Cirque Pinnacle SPI driver to read data correctly (#17074)Kyle McCreery2022-05-121-4/+5
| |
* | Add support for multiple sensors to pmw3360 (#15996)uqs2022-04-192-82/+89
|/
* analog.[ch]: remove unnecessary includes (#16471)Ryan2022-03-041-0/+2
|
* Format code according to conventions (#16322)QMK Bot2022-02-1212-53/+71
|
* [Bug][Core] Fix optical sensor firmware upload (#15919)Drashna Jaelre2022-01-204-19/+11
|
* PMW3389 Revert Firmware load during Initilization (#15859)Alabastard-642022-01-131-4/+2
|
* Add PMW3389 optical sensor Support (Updated) (#15740)Alabastard-642022-01-115-292/+654
| | | Co-authored-by: Drashna Jaelre <drashna@live.com>
* Optimize initialization of PMW3360 Sensor (#15821)Drashna Jaelre2022-01-101-0/+4
|
* Format code according to conventions (#15705)QMK Bot2022-01-021-1/+1
|
* Update pmw3360 comments to match the datasheet better, fix delays. (#15682)uqs2022-01-021-12/+22
|
* Merge remote-tracking branch 'origin/master' into developQMK Bot2021-12-311-2/+2
|\
| * [Bug] Fix analog joystick to mouse compilation (#15677)Dasky2021-12-301-2/+2
| |
* | Format code according to conventions (#15604)QMK Bot2021-12-282-8/+6
| |
* | pwm3360 driver cleanup and diff reduction to adns9800 (#15559)uqs2021-12-273-143/+131
| | | | | | | | | | | | | | | | | | | | | | | | * Diff reduction between ADNS9800 and PMW3360 drivers. They are very similar devices. This (somewhat) unreadable diff is essentially a no-op, but it makes a `vimdiff` between the 2 drivers much more readable. * Cleanup pwm3360 driver some more. Remove redundant calls to spi_start() and spi_stop(), as pmw3360_write() will already call these.
* | Fix for SPI write timing in PMW3360 driver (#15519)Alabastard-642021-12-271-3/+3
| | | | | | | | | | | | Timing does not match Pixart documentation for this sensor (may have been carried forward from adns9800). Not aware of any issues coming from this currently. It should only cause issues when writing to multiple registers in succession which currently only happens during initialization for the PMW3360. This should prevent future issues with write operations if other features of the sensor are added.
* | [Core] Split support for pointing devices. (#15304)Dasky2021-12-272-9/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Draft implementation * formatting * fix combined buttons * remove pimoroni throttle * sync pointing on a throttle loop with checksum * no longer used * doh Co-authored-by: Drashna Jaelre <drashna@live.com> * switch pimoroni to a cpi equivalent * add cpi support * allow user modification of seperate mouse reports * a little tidy up * add *_RIGHT defines. * docs * doxygen comments * basic changelog * clean up pimoroni * small doc fixes * Update docs/feature_pointing_device.md Co-authored-by: Drashna Jaelre <drashna@live.com> * performance tweak if side has usb * Don't run init funtions on wrong side * renamed some variables for consistency * fix pimoroni typos * Clamp instead of OR * Promote combined values to uint16_t * Update pointing_device.c Co-authored-by: Drashna Jaelre <drashna@live.com> Co-authored-by: Nick Brassel <nick@tzarc.org>
* | Merge remote-tracking branch 'origin/master' into developQMK Bot2021-12-152-4/+3
|\|
| * [Core] Fix Sensor driver code (#15484)Drashna Jaelre2021-12-152-4/+3
| |
* | Merge remote-tracking branch 'origin/master' into developDrashna Jael're2021-12-112-0/+6
|\|
| * [Core] Add configuration of PMW3360 lift off distance (#15424)Xelus222021-12-082-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | * sensor code add * update documentation * add default #define * Update drivers/sensors/pmw3360.c Co-authored-by: Drashna Jaelre <drashna@live.com> Co-authored-by: Drashna Jaelre <drashna@live.com>
* | Expand rotational range for PMW3360 Optical Sensor (#15431)Drashna Jaelre2021-12-081-1/+1
|/
* Rework and expand Pointing Device support (#14343)Drashna Jaelre2021-11-1417-437/+1281
| | | Co-authored-by: Dasky <32983009+daskygit@users.noreply.github.com>
* Manually format develop (#15003)Joel Challis2021-11-016-149/+130
|
* Tidy up ADNS9800 and PMW3360 firmware blobs (#14936)Ryan2021-10-244-3355/+461
|
* [Core] Fix copypasta issue with pmw3360 sensor config (#14106)Drashna Jaelre2021-08-211-1/+1
|
* Improve pmw3360 sensor and make it more hardware agnostic (#14097)Drashna Jaelre2021-08-202-74/+87
|
* [Core] Speed up pimoroni trackball driver (#13823)Dasky2021-08-192-90/+153
|