Searched refs:will (Results 576 – 600 of 1633) sorted by relevance
1...<<21222324252627282930>>...66
| /Zephyr-latest/drivers/sensor/hp206c/ |
| D | Kconfig | 37 Value, in cm, that will be used to compensate altitude calculation.
|
| /Zephyr-latest/subsys/bindesc/ |
| D | gen_bindesc_build_time_h.cmake | 17 # remove leading zeros so that the output will not be interpreted as octal
|
| /Zephyr-latest/soc/espressif/esp32c6/ |
| D | Kconfig | 25 If enabled, the MAC and baseband of Wi-Fi and Bluetooth will be powered
|
| /Zephyr-latest/samples/boards/st/power_mgmt/serial_wakeup/boards/ |
| D | b_u585i_iot02a.overlay | 26 /* Configure sleep pinctrl configuration which will be used when
|
| /Zephyr-latest/samples/sensor/sgp40_sht4x/ |
| D | Kconfig | 20 int "RH [%] threshold above which the heater will be activated"
|
| /Zephyr-latest/cmake/bintools/llvm/ |
| D | target.cmake | 10 # Extract the clang version. Debian (maybe other distros?) will
|
| /Zephyr-latest/samples/boards/nxp/adsp/number_crunching/ |
| D | CMakeLists.txt | 17 # contains a "proprietary" library we will link to
|
| /Zephyr-latest/samples/drivers/auxdisplay/ |
| D | README.rst | 29 If successful, the display will show "Hello World from <board>".
|
| /Zephyr-latest/samples/bluetooth/direction_finding_peripheral/boards/ |
| D | nrf52833dk_nrf52833.overlay | 19 * Radio peripheral. The pins will be acquired by Radio to
|
| /Zephyr-latest/samples/bluetooth/direction_finding_central/boards/ |
| D | nrf52833dk_nrf52833.overlay | 19 * Radio peripheral. The pins will be acquired by Radio to
|
| /Zephyr-latest/boards/arm/mps2/ |
| D | Kconfig.defconfig | 41 # will still permit bus access.
|
| /Zephyr-latest/boards/nxp/common/ |
| D | segger-ecc-systemview.rst | 16 control block a fault will occur, provided that ECC is enabled and the RAM
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob.rst | 22 scheduling it to periods with low network traffic, will offer significant improvements on the speed
80 When operating in Pull BLOB Transfer Mode, the BLOB Transfer Server will request a small number of
100 used, and the BLOB Transfer models will move around inside the BLOB's data in blocks and chunks,
145 will transfer the BLOB with the highest possible block and chunk size.
155 In Push BLOB Transfer Mode, the send rate is controlled by the BLOB Transfer Client, which will push
159 In Pull BLOB Transfer Mode, the BLOB Transfer Server will "pull" the chunks from the BLOB Transfer
162 in Pull BLOB Transfer Mode, the BLOB Transfer Server will request chunks from the BLOB Transfer
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | index.rst | 90 will block the calling thread until either the timeout expires, the target
94 Once a thread has terminated, the kernel guarantees that no use will
198 If it is known that a thread will never run in user mode, or the stack is
202 These stacks save memory because an MPU region will never need to be
203 programmed to cover the stack buffer itself, and the kernel will not need
207 Attempts from user mode to use stacks declared in this way will result in
216 If it is known that a stack will need to host user threads, or if this
290 interrupt context. The intent is that this feature will be used to
292 in driver subsystems. The thread, once woken, will be guaranteed to
346 If :kconfig:option:`CONFIG_USERSPACE` is enabled, this thread will be created in
[all …]
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig.cc2520 | 73 This option will expose the hardware AES encryption from CC2520.
75 The crypto device exposed will only support synchronous CCM operation.
|
| /Zephyr-latest/drivers/watchdog/ |
| D | Kconfig.nxp_fs26 | 58 If the device is started in DEBUG mode, the driver will exit this mode
60 mode and this driver is enabled, it will fail to initialize.
|
| /Zephyr-latest/doc/develop/api/ |
| D | overview.rst | 27 * All existing stable APIs in Zephyr will be start with version 1.0.0.
51 Changes to APIs in the future will require adapting the version following the
|
| /Zephyr-latest/doc/services/file_system/ |
| D | index.rst | 42 - ``FATFS_MNTP`` is the mount point where the file system will be mounted.
43 - ``fat_fs`` is the file system data which will be used by fs_mount() API.
|
| /Zephyr-latest/samples/bluetooth/bap_broadcast_sink/ |
| D | README.rst | 21 (empty string), sink device will listen to all available broadcast sources.
70 Note this will produce a Linux executable in :file:`./build/zephyr/zephyr.exe`.
|
| /Zephyr-latest/samples/subsys/smf/hsm_psicc2/ |
| D | README.rst | 50 PSiCC2 Section 2.3.15. The differences will not be listed here as it is hoped :ref:`SMF <smf>`
51 will support these transitions in the future and the list would become outdated.
|
| /Zephyr-latest/drivers/entropy/ |
| D | Kconfig.nrf5 | 49 buffer goes below this number hardware entropy generation will be
67 buffer goes below this number hardware entropy generation will be
|
| D | Kconfig.stm32 | 35 buffer goes below this number hardware entropy generation will be
53 buffer goes below this number hardware entropy generation will be
|
| /Zephyr-latest/samples/net/sockets/echo_async_select/ |
| D | README.rst | 43 After a connection is made, the application will echo back any line sent to
54 Linux. (Note: if you look at the source, you will see that the code is
|
| /Zephyr-latest/boards/qemu/cortex_r5/doc/ |
| D | index.rst | 6 This board configuration will use QEMU to emulate the Xilinx Zynq UltraScale+
72 This will build an image with the synchronization sample app, boot it using
|
| /Zephyr-latest/boards/qemu/malta/doc/ |
| D | index.rst | 6 This board configuration will use QEMU to emulate the MIPS Malta platform.
66 This will build an image with the synchronization sample app, boot it using
|
1...<<21222324252627282930>>...66
