Performance tuning

Author: dhl

boards/shields/charybdis/charybdis.dtsi

@@ -1,5 +1,4 @@
 #include <dt-bindings/zmk/matrix_transform.h>
-#include <dt-bindings/led/led.h>
 
 / {
     chosen {

boards/shields/charybdis/charybdis_left.overlay

@@ -10,3 +10,11 @@
 		, <&gpio1 4  GPIO_ACTIVE_HIGH>
 		;
 };
+
+&spi0 {
+	status = "disabled";
+};
+
+&trackball {
+	status = "disabled";
+};

boards/shields/charybdis/charybdis_right.conf

@@ -1,10 +1,17 @@
 CONFIG_SPI=y
 CONFIG_INPUT=y
 CONFIG_ZMK_POINTING=y
+
+CONFIG_ZMK_EXT_POWER=y
+
 CONFIG_PMW3610=y
 CONFIG_PMW3610_SWAP_XY=y
 CONFIG_PMW3610_INVERT_X=y
 CONFIG_PMW3610_INVERT_Y=y
+
+; CONFIG_PMW3610_RUN_DOWNSHIFT_TIME_MS=3264
+; CONFIG_PMW3610_REST1_SAMPLE_TIME_MS=40
+
 CONFIG_PMW3610_SMART_ALGORITHM=y
 
-CONFIG_ZMK_EXT_POWER=y
+CONFIG_PMW3610_REPORT_INTERVAL_MIN=12

boards/shields/charybdis/charybdis_right.overlay

@@ -4,7 +4,7 @@
 
 &default_transform {
     col-offset = <6>;
-}; 
+};
 
 &kscan0 {
 	col-gpios
@@ -56,7 +56,7 @@
         x-input-code = <INPUT_REL_X>;
         y-input-code = <INPUT_REL_Y>;
 
-        force-awake;
+        // for0ce-awake;
         /* keep the sensor awake while ZMK activity state is ACTIVE,
            fallback to normal downshift mode after ZMK goes into IDLE / SLEEP mode.
            thus, the sensor would be a `wakeup-source` */

config/charybdis.conf

@@ -1,11 +1,11 @@
 CONFIG_BT_CTLR_TX_PWR_PLUS_8=y
-CONFIG_ZMK_BATTERY_REPORT_INTERVAL=60
 
-# Power Management
-CONFIG_ZMK_SLEEP=y
-CONFIG_ZMK_IDLE_SLEEP_TIMEOUT=3600000
-CONFIG_ZMK_IDLE_TIMEOUT=30000
+; CONFIG_BT_PERIPHERAL_PREF_MAX_INT=9
+; CONFIG_BT_PERIPHERAL_PREF_LATENCY=16
+; CONFIG_BT_BUF_ACL_TX_COUNT=32
+; CONFIG_BT_L2CAP_TX_BUF_COUNT=32
 
-# Bluetooth Stability
-CONFIG_BT_CTLR_PHY_2M=n
-CONFIG_ZMK_SPLIT_BLE_CENTRAL_POSITION_QUEUE_SIZE=10
+CONFIG_ZMK_BLE_EXPERIMENTAL_CONN=y
+; CONFIG_ZMK_SPLIT_BLE_CENTRAL_BATTERY_LEVEL_FETCHING=y
+; CONFIG_ZMK_SPLIT_BLE_CENTRAL_BATTERY_LEVEL_PROXY=y
+; CONFIG_ZMK_BEHAVIORS_QUEUE_SIZE=512