-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Core encoder/sensor refactor #1039
Core encoder/sensor refactor #1039
Conversation
If it's alright I'll send you a revised rotr folder with a better keymap and a few definition tweaks to match the bt60s |
2eb4df3
to
0838fa9
Compare
867ef6a
to
ef57a53
Compare
326a540
to
b45a26b
Compare
98a3d97
to
c87e149
Compare
c87e149
to
fe08e17
Compare
adae294
to
d557438
Compare
app/Kconfig
Outdated
@@ -482,8 +494,12 @@ config ZMK_WPM | |||
bool "Calculate WPM" | |||
default n | |||
|
|||
config SENSOR | |||
DT_COMPAT_ZMK_KEYMAP_SENSORS := zmk,keymap-sensors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does battery.c require SENSOR
be enabled?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure does. Added a new commit here that creates a new ZMK_BATTERY_REPORTING
Kconfig symbol:
config ZMK_BATTERY_REPORTING
bool "Battery level detection/reporting"
default n
select SENSOR
select BT_BAS if ZMK_BLE
That is imply
d by ZMK_BLE
automatically.
Thoughts?
f51b3fa
to
dd224e1
Compare
a7e2e61
to
2ea2a14
Compare
f37414d
to
5e4abe0
Compare
db70caf
to
f3450ca
Compare
|
||
if ZMK_KEYMAP_SENSORS | ||
|
||
config ZMK_KEYMAP_SENSORS_DEFAULT_TRIGGERS_PER_ROTATION |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the difference between this and ZMK_ENCODERS_DEFAULT_TRIGGERS_PER_ROTATION
? Do we need two different configs (with different defaults) that seem to be for the same thing?
* Refactor sensor events to include channel data, necessary for prop split encoders, and avoiding duplicate calls, to fetch channel data twice, etc. * More consistent behavior driver API. * Allow setting triggers per resolution at the behavior level optionally.
* Add new `steps` property to the `aips,ec11` binding, to make the driver properly report degrees in the rotation delta channel. * Handle old sensor values in sensor rotate behavior.
* Don't force on SENSOR Kconfig setting unless needed based on the detected DT.
* Bump the default stack size for the HoG processing thread to avoid issues w/ some pathways.
* Move to new steps/triggers-per-rotation config. * Leverage QDEC Nordic driver when used on Nordic DK.
* Add dedicated battery reporting Kconfig that is `imply`d by enabling ZMK_BLE.
* All sensor behaviors should see sensor data, then selectively only have some trigger their behaviors.
f3450ca
to
b05c1af
Compare
b05c1af
to
471dddb
Compare
* Document changed configuration, support for other Zephyr drivers, next steps. Co-authored-by: Cem Aksoylar <[email protected]>
471dddb
to
8cfbd64
Compare
Some major refactors to sensors: