You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add-on hardware support (eg. audio, RGB, OLED screen, etc.)
Alteration (enhancement/optimization) of existing feature(s)
New behavior
Description
What I want to achieve: have a haptic feedback feature on split keyboard using I2C-based driver (eg. DRV2605-L)
Constraints: this driver typically does not have alternate address, therefore if I need to use this driver on both side, it won't work due to address conflict
Possible approaches: I am not sure if there is work-around to have multiple I2c devices with same address, but another approach is by using different I2C buses on each half for each driver. From what I understand, this is not yet supported on QMK (or, would be great if you can give me a guidance on how to use this, if it is already supported)
thank you!
The text was updated successfully, but these errors were encountered:
Feature Request Type
Description
What I want to achieve: have a haptic feedback feature on split keyboard using I2C-based driver (eg. DRV2605-L)
Constraints: this driver typically does not have alternate address, therefore if I need to use this driver on both side, it won't work due to address conflict
Possible approaches: I am not sure if there is work-around to have multiple I2c devices with same address, but another approach is by using different I2C buses on each half for each driver. From what I understand, this is not yet supported on QMK (or, would be great if you can give me a guidance on how to use this, if it is already supported)
thank you!
The text was updated successfully, but these errors were encountered: