Searched refs:decide (Results 1 – 25 of 39) sorted by relevance
12
/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/samples/subsys/mgmt/updatehub/ |
D | Kconfig | 10 there is an available update, also requires the user to decide if
|
D | README.rst | 23 an available update, also requires the user to decide if it is appropriate to
|
/Zephyr-latest/subsys/mgmt/ec_host_cmd/ |
D | Kconfig.logging | 11 to decide, if full reqest and response buffers are logged alongside
|
/Zephyr-latest/doc/build/dts/ |
D | dt-vs-kconfig.rst | 8 sometimes be confusing. This section should help you decide which one to use.
|
D | troubleshooting.rst | 200 where ``CONFIG_FOO`` is the option that :file:`CMakeLists.txt` uses to decide
|
/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
|
D | device_runtime.rst | 62 device. An application can, however, decide when to disable or enable runtime
|
/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/cmake/modules/ |
D | FindZephyr-sdk.cmake | 12 # SDK and based on user / environment settings of selected toolchain decide if
|
/Zephyr-latest/cmake/linker_script/arm/ |
D | linker.cmake | 35 # ToDo: decide on the optimal location for this.
|
/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/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/doc/develop/toolchains/ |
D | zephyr_sdk.rst | 43 by running the setup script. If you decide not to register the Zephyr SDK in the CMake registry,
|
/Zephyr-latest/doc/develop/west/ |
D | basics.rst | 180 It then uses the manifest file to decide where missing projects should be
|
/Zephyr-latest/soc/intel/intel_adsp/cavs/include/ |
D | xtensa-cavs-linker.ld | 401 * binutils to decide to warn about (no way to turn that off, it
|
/Zephyr-latest/doc/project/ |
D | tsc.rst | 195 Abstentions do not impact the number of votes needed to decide a vote.
|
/Zephyr-latest/doc/develop/test/ |
D | bsim.rst | 57 built with some checks which decide if the test is passing or failing. These embedded
|
D | ztest.rst | 22 :c:func:`ztest_run_all` and should return a boolean to decide if the suite should run. 382 and are used to decide whether a test failed or passed by verifying whether an
|
/Zephyr-latest/doc/kernel/services/smp/ |
D | smp.rst | 101 kernel scheduler to decide on which threads to execute. Zephyr 359 still decide to implement its context switching using
|
/Zephyr-latest/soc/intel/intel_adsp/ace/ |
D | ace-link.ld | 495 * binutils to decide to warn about (no way to turn that off, it
|
/Zephyr-latest/doc/connectivity/bluetooth/ |
D | bluetooth-le-host.rst | 43 when creating an application is to decide which roles are needed and go
|
/Zephyr-latest/doc/services/ipc/ipc_service/backends/ |
D | ipc_service_icbmsg.rst | 181 It is up to the implementation to decide what to do if no blocks are available.
|
12