Bryan Forbes 72f8c5072e Update global behaviors to be compiled in based on their Kconfig option ... Because global behaviors have to exist on both the central and split regardless if the user references them in their keymap, we can't omit the behavior declaration if the user doen't reference it and decide to compile it later based on the existence of the behavior declaration. The best option seems to be to decide whether to compile those behaviors based on the feature Kconfig flag. This also means that the two reset behaviors will always be compiled into both sides.		2024-03-06 11:40:49 -06:00
..
behaviors	Update global behaviors to be compiled in based on their Kconfig option	2024-03-06 11:40:49 -06:00
bindings	feat(behaviors): hold while undecided	2024-02-20 00:25:53 -08:00
common	refactor: Replace tabs with spaces	2023-04-24 16:07:04 -07:00
behaviors.dtsi	feat(mouse): Initial mouse keys support.	2023-11-15 11:16:59 -08:00