|
| 1 | +# |
| 2 | +# Copyright (c) 2023 Nordic Semiconductor |
| 3 | +# |
| 4 | +# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause |
| 5 | +# |
| 6 | + |
| 7 | +if CHIP |
| 8 | + |
| 9 | +config MATTER_APP_TASK_QUEUE_SIZE |
| 10 | + int "Maximum number of tasks delegated to be run in the application queue" |
| 11 | + default 10 |
| 12 | + help |
| 13 | + Define the maximum size of the queue dedicated for application tasks that |
| 14 | + have to be run in the application thread context. |
| 15 | + |
| 16 | +config MATTER_APP_TASK_MAX_SIZE |
| 17 | + int "Maximum size of application task in bytes" |
| 18 | + default 16 |
| 19 | + help |
| 20 | + Defines the maximum size of a functor that can be put in the application |
| 21 | + thread's task queue. |
| 22 | + |
| 23 | +config MATTER_CUSTOM_BLUETOOTH_ADVERTISING |
| 24 | + bool "Define the custom behavior of the Bluetooth advertisement in the application code" |
| 25 | + help |
| 26 | + Disable the default Bluetooth advertising start which is defined in the board.cpp file and |
| 27 | + allows to use the custom one. |
| 28 | + |
| 29 | +config MATTER_OPERATIONAL_KEYS_MIGRATION_TO_ITS |
| 30 | + bool "Operational keys migration feature" |
| 31 | + depends on CHIP_CRYPTO_PSA |
| 32 | + help |
| 33 | + Enables migration of the operational keys stored in the persistent storage to the PSA ITS secure storage. |
| 34 | + Enable this feature while updating the firmware of in-field devices that run Mbed TLS cryptography backend |
| 35 | + to the firmware based on PSA Crypto API. |
| 36 | + |
| 37 | +config MATTER_FACTORY_RESET_ON_KEY_MIGRATION_FAILURE |
| 38 | + bool "Perform factory reset if the operational key migration failed" |
| 39 | + default y |
| 40 | + depends on MATTER_OPERATIONAL_KEYS_MIGRATION_TO_ITS |
| 41 | + help |
| 42 | + Allow device to perform factory reset if the operational key for Fabric has not been migrated |
| 43 | + properly to PSA ITS storage. |
| 44 | + |
| 45 | +config MATTER_LEDS |
| 46 | + bool "LEDs usage" |
| 47 | + default y |
| 48 | + depends on DK_LIBRARY |
| 49 | + help |
| 50 | + Enables LEDs module to be used in the application. |
| 51 | + |
| 52 | +config MATTER_SETTINGS_SHELL |
| 53 | + bool "Settings shell for Matter purposes" |
| 54 | + default y if CHIP_MEMORY_PROFILING |
| 55 | + depends on SHELL |
| 56 | + depends on NVS || ZMS |
| 57 | + help |
| 58 | + Allows using matter_settings shell commands. |
| 59 | + You can use the following commands: |
| 60 | + peak - to read the maximum settings usage. |
| 61 | + reset - to reset peak value. |
| 62 | + get_size - to read the size of specific value. |
| 63 | + current - to read current settings usage. |
| 64 | + free - to read free settings space. |
| 65 | + |
| 66 | +config MATTER_TEST_EVENT_TRIGGERS |
| 67 | + bool "Test event triggers support" |
| 68 | + default y |
| 69 | + help |
| 70 | + Enables support for test event triggers for the specific use-cases. |
| 71 | + |
| 72 | +config MATTER_TEST_EVENT_TRIGGERS_MAX |
| 73 | + int "Maximum amount of event triggers" |
| 74 | + default 8 |
| 75 | + depends on MATTER_TEST_EVENT_TRIGGERS |
| 76 | + help |
| 77 | + Defines the maximum amount of event triggers. |
| 78 | + |
| 79 | +config MATTER_TEST_EVENT_TRIGGERS_REGISTER_DEFAULTS |
| 80 | + bool "Register default triggers for Matter sample" |
| 81 | + depends on MATTER_TEST_EVENT_TRIGGERS |
| 82 | + default y |
| 83 | + help |
| 84 | + Automatically register default triggers such as factory reset, |
| 85 | + device reboot, OTA start query. |
| 86 | + |
| 87 | +config MATTER_TEST_EVENT_TRIGGERS_MAX_TRIGGERS_DELEGATES |
| 88 | + int "Maximum amount of the trigger delegates" |
| 89 | + default 3 |
| 90 | + depends on MATTER_TEST_EVENT_TRIGGERS |
| 91 | + help |
| 92 | + Defines the maximum number for the TestEventTriggerDelegate implementations |
| 93 | + to be registered in the nRF test event triggers class. |
| 94 | + |
| 95 | +config MATTER_TEST_SHELL |
| 96 | + bool "Test - specific shell commands support for Matter samples" |
| 97 | + depends on CHIP_LIB_SHELL |
| 98 | + help |
| 99 | + Enables support for test - specific shell commands in Matter samples. |
| 100 | + |
| 101 | +config MATTER_PERSISTENT_STORAGE |
| 102 | + bool "Persistent storage support for Matter samples" |
| 103 | + help |
| 104 | + Matter persistent storage support with the configurable backend. |
| 105 | + |
| 106 | +config MATTER_ZAP_FILE_PATH |
| 107 | + string "Path in sample, under which ZAP file is located" |
| 108 | + help |
| 109 | + Absolute path to location under which ZAP file is located. |
| 110 | + It shall contain the file name and .zap extension. |
| 111 | + |
| 112 | +config MATTER_CERTIFICATION |
| 113 | + bool "Patches for Matter platform certification" |
| 114 | + help |
| 115 | + It enables including software patches required for the Matter platform certification |
| 116 | + purposes. Currently it works only with the Matter template sample. |
| 117 | + |
| 118 | +config MATTER_USE_DEFAULT_BUTTON_HANDLER |
| 119 | + bool "Use default button handler alongside the application one" |
| 120 | + default y |
| 121 | + help |
| 122 | + When enabled, the button handler responsible for factory reset and DFU is used alongside |
| 123 | + application handler. In order to override this handler, disable this config. |
| 124 | + |
| 125 | +choice MATTER_ZAP_GENERATION_MODE |
| 126 | + prompt "Matter ZAP generation mode" |
| 127 | + default MATTER_ZAP_GENERATION_STATIC |
| 128 | + |
| 129 | +config MATTER_ZAP_GENERATION_BUILD_TIME |
| 130 | + bool "Generate ZAP artifacts at build time" |
| 131 | + |
| 132 | +config MATTER_ZAP_GENERATION_STATIC |
| 133 | + bool "Use pre-generated ZAP artifacts" |
| 134 | +endchoice |
| 135 | + |
| 136 | +rsource "persistent_storage/Kconfig" |
| 137 | +rsource "watchdog/Kconfig" |
| 138 | +rsource "diagnostic/Kconfig" |
| 139 | + |
| 140 | +endif # CHIP |
0 commit comments