Searched refs:valid (Results 151 – 175 of 252) sorted by relevance
1234567891011
| /Zephyr-latest/doc/services/tfm/ |
| D | overview.rst | 91 valid, have not been tampered with, and come from a reliable source. The
264 Generally, you simply need to select the ``*/ns`` board target of a valid board
|
| D | build.rst | 6 When building a valid ``_ns`` board target, TF-M will be built in the
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 128 request in the issue tracker. Commits without a valid reference
180 to determine if they are valid before they are accepted; this
|
| /Zephyr-latest/doc/build/dts/ |
| D | troubleshooting.rst | 43 where ``NODE_ID`` is a valid :ref:`node identifier <dt-node-identifiers>`, but
330 isn't referring to a valid node. :ref:`get-devicetree-outputs` and debug from
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | friend.c | 103 bool valid, bool established) in bt_mesh_friend_find() argument
112 if (valid && !friend_is_allocated(frnd)) { in bt_mesh_friend_find()
174 if (frnd->subnet->keys[i].valid) { in friend_clear()
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | syscalls.rst | 265 ensure that the semaphore object passed in is a valid semaphore and that
271 * Any other arguments that have a limited range of valid values.
283 a valid kernel object of the expected type, that the calling thread
326 a provided pointer is a valid instance of a specific device driver, that
|
| /Zephyr-latest/drivers/net/ |
| D | Kconfig | 64 bool "Verify that received FCS is valid"
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | virtual_memory.rst | 191 function does not check if it is a valid mapped region before unmapping.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | brg_cfg.rst | 138 - Messages with an IVISeq less than or equal to the stored value are discarded, while valid messages
|
| /Zephyr-latest/cmake/compiler/gcc/ |
| D | compiler_flags.cmake | 175 # Only a valid option with GCC 7.x and above, so let's do check and set.
|
| /Zephyr-latest/doc/services/retention/ |
| D | index.rst | 121 will be set on the area, and it will be marked as valid from that point
|
| /Zephyr-latest/doc/develop/tools/ |
| D | clion.rst | 13 valid if you prefer to use CMake.
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_WINDOWS.rst | 62 indicating it's valid. If it does not, the registers must have been
|
| /Zephyr-latest/tests/bluetooth/controller/ctrl_hci/src/ |
| D | main.c | 264 conn_from_pool->llcp.fex.valid = 1; in ZTEST()
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | hci.txt | 1071 of the event parameters. The subevent code shall be set to one of the valid
1484 | 0x8000 | No valid sample available or sample |
1497 | 0x8000 | No valid sample available or sample |
1671 | 0x8000 | No valid sample available or sample |
1684 | 0x8000 | No valid sample available or sample |
|
| /Zephyr-latest/subsys/bluetooth/controller/ll_sw/ |
| D | ull_llcp.c | 815 if (!conn->llcp.fex.valid) { in ull_cp_cis_create()
1258 if ((conn->llcp.fex.valid &&
1260 (!conn->llcp.fex.valid && !feature_cte_req(conn))) {
|
| /Zephyr-latest/subsys/logging/ |
| D | log_core.c | 850 log_msg->hdr.desc.valid = 0; in z_log_msg_enqueue()
|
| /Zephyr-latest/boards/ti/cc1352r_sensortag/doc/ |
| D | index.rst | 220 bootloader will start if there is no valid application image in flash or the
|
| /Zephyr-latest/boards/nxp/mimxrt595_evk/ |
| D | mimxrt595_evk_mimxrt595s_cm33.dts | 452 data-valid-time = <1>;
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_1.rst | 105 A response will only contain information for valid images, if an image can not
106 be identified as valid it is simply skipped.
|
| /Zephyr-latest/modules/mbedtls/ |
| D | Kconfig.tls-generic | 448 There also need to be a valid time source in the system, as mbedTLS
449 expects a valid date/time for certificate validation."
|
| /Zephyr-latest/dts/arm/microchip/ |
| D | mec1501hsz.dtsi | 74 clk32kmon-valid-min = <4>;
|
| /Zephyr-latest/soc/andestech/ae350/ |
| D | linker.ld | 422 /* Because ROMABLE_REGION != RAMABLE_REGION in XIP-system, it is valid
|
| /Zephyr-latest/boards/st/stm32wb5mm_dk/doc/ |
| D | stm32wb5mm_dk.rst | 130 a valid STM32WB Coprocessor binaries (either 'Full stack' or 'HCI Layer').
|
| /Zephyr-latest/doc/develop/west/ |
| D | basics.rst | 78 repository. The only requirement is that it contains a valid manifest file.
|
1234567891011
