Searched full:decide (Results 1 – 25 of 101) sorted by relevance
12345
/Zephyr-latest/dts/bindings/sensor/ |
D | nxp,lpcmp.yaml | 20 Decide whether to enable the comparator is available in selected pin. 25 Decide whether to use the unfiltered output. 30 Decide whether to invert the comparator output.
|
/Zephyr-latest/arch/arc/core/secureshield/ |
D | secure_sys_services.c | 22 * to decide whether the access is valid. 37 * to decide whether the access is valid. 63 * apply one. Necessary check should be done to decide whether the apply is
|
/Zephyr-latest/cmake/toolchain/llvm/ |
D | clang_libgcc.cfg | 5 # decide to return path to libclang_rt.* if its default
|
/Zephyr-latest/samples/subsys/mgmt/hawkbit/ |
D | Kconfig | 24 there is an available update, also requires the user to decide if
|
/Zephyr-latest/subsys/mgmt/ec_host_cmd/ |
D | Kconfig.logging | 11 to decide, if full reqest and response buffers are logged alongside
|
/Zephyr-latest/samples/subsys/mgmt/updatehub/ |
D | Kconfig | 10 there is an available update, also requires the user to decide if
|
/Zephyr-latest/subsys/bluetooth/audio/ |
D | Kconfig.mctl | 9 # TODO: Decide, and add, top-level namespace prefix (currently none) to symbols.
|
/Zephyr-latest/samples/boards/st/power_mgmt/stop3/src/ |
D | main.c | 34 * User can decide to not use this feature to further reduce power consumption in main()
|
/Zephyr-latest/tests/subsys/canbus/isotp/conformance/ |
D | testcase.yaml | 11 # The test-specific CONFIG_TEST_USE_CAN_FD_MODE is used to decide if the test should use
|
/Zephyr-latest/include/zephyr/mgmt/mcumgr/grp/fs_mgmt/ |
D | fs_mgmt.h | 65 * returned as "len", the user application needs to decide how to handle this (e.g. the
|
/Zephyr-latest/include/zephyr/net/ |
D | socket_net_mgmt.h | 71 * sockets. Application can decide how the pid is constructed.
|
D | net_core.h | 105 /** Packet has not been touched, other part should decide about its
|
/Zephyr-latest/doc/build/dts/ |
D | dt-vs-kconfig.rst | 8 sometimes be confusing. This section should help you decide which one to use.
|
/Zephyr-latest/subsys/sensing/ |
D | sensor_mgmt.h | 108 /* this function is used to decide whether filtering sensitivity checking
|
/Zephyr-latest/doc/develop/api/ |
D | api_lifecycle.rst | 167 opened on GitHub. It is left to the person proposing the change to decide 260 The Zephyr maintainers will decide when to actually remove the API: this
|
/Zephyr-latest/subsys/bluetooth/host/ |
D | uuid.c | 18 /* TODO: Decide whether to continue using BLE format or switch to RFC 4122 */
|
/Zephyr-latest/soc/espressif/common/ |
D | Kconfig.esptool | 16 This config option helps decide whether flash is Quad or Octal, but please note some limitations:
|
/Zephyr-latest/share/zephyr-package/cmake/ |
D | ZephyrConfig.cmake | 5 # The purpose of this files is to allow users to decide if they want to:
|
/Zephyr-latest/doc/services/pm/ |
D | system.rst | 119 to decide which power state the system should transition to based on the
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | core.rst | 50 by calling :c:func:`bt_mesh_rpl_pending_store`. This is up to the node to decide,
|
/Zephyr-latest/tests/bsim/bluetooth/host/gatt/settings/src/ |
D | server.c | 157 * reason, we decide to reboot before the delayed store work item has had the
|
/Zephyr-latest/drivers/watchdog/ |
D | wdt_cc13xx_cc26xx.c | 187 * to decide (by calling `_feed()`) in wdt_cc13xx_cc26xx_isr()
|
/Zephyr-latest/cmake/modules/ |
D | FindZephyr-sdk.cmake | 12 # SDK and based on user / environment settings of selected toolchain decide if
|
/Zephyr-latest/kernel/ |
D | smp.c | 145 /* Let scheduler decide what thread to run next. */ in smp_init_top()
|
/Zephyr-latest/cmake/linker_script/arm/ |
D | linker.cmake | 35 # ToDo: decide on the optimal location for this.
|
12345