kb01/zmk
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

build failures because enum starts at 1?

Browse source
This commit is contained in:
jding 2021-10-30 15:46:54 +00:00
parent 26a6fbfefb
commit caad69a37d
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
app/src/behaviors/behavior_hold_tap.c
View file

@ -659,12 +659,12 @@ static struct behavior_hold_tap_data behavior_hold_tap_data;
DEVICE_DT_INST_DEFINE(n, behavior_hold_tap_init, device_pm_control_nop, \
&behavior_hold_tap_data, &behavior_hold_tap_config_##n, APPLICATION, \
CONFIG_KERNEL_INIT_PRIORITY_DEFAULT, &behavior_hold_tap_driver_api); \
BUILD_ASSERT((DT_ENUM_IDX(DT_DRV_INST(n), flavor) == 3 && \
BUILD_ASSERT((DT_ENUM_IDX(DT_DRV_INST(n), flavor) == 4 && \
!(DT_INST_PROP_LEN(n, hold_trigger_key_positions) > 0)), \
"'hold-trigger-key-positions' must be non-empty if hold-tap flavor is " \
"'tap-positionally-preferred'"); \
BUILD_ASSERT((DT_INST_PROP_LEN(n, hold_trigger_key_positions) > 0) \
&& DT_ENUM_IDX(DT_DRV_INST(n), flavor) != 3 ), \
&& DT_ENUM_IDX(DT_DRV_INST(n), flavor) != 4 ), \
"hold-tap flavor must be 'tap-positionally-preferred' if 'hold-trigger-key-positions' is non-empty");
DT_INST_FOREACH_STATUS_OKAY(KP_INST)