Searched refs:long (Results 76 – 100 of 201) sorted by relevance
123456789
| /Zephyr-latest/samples/subsys/fs/zms/ |
| D | README.rst | 18 #. A long set of data (128 bytes)
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.stats | 147 suspended, for how long the last time and on average.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_config.rst | 35 ":kconfig:option:`CONFIG_NET_CONFIG_INIT_TIMEOUT`", "This tells how long to wait for
|
| D | lwm2m.rst | 414 …this completely removes the handshake when device resumes operation after long idle period. Greatl…
690 …- The lifetime parameter in LwM2M specifies how long a device's registration with an LwM2M server …
696 - How long the client can stay idle before sending a next update.
718 is the earliest when any of these values expire. This allows setting long lifetime for the
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | gatt.rst | 56 thus it is not recommended to block for long periods of time in them.
|
| /Zephyr-latest/drivers/wifi/esp_at/ |
| D | Kconfig.esp_at | 92 How long to wait for device to become ready after AT+RST has been
|
| /Zephyr-latest/doc/releases/ |
| D | index.rst | 27 long term support releases approximately every 2 years. Periodic and non-LTS
|
| D | release-notes-1.6.rst | 245 * ``ZEP-989`` - Cache next ready thread instead of finding out the long way
292 * ``ZEP-724`` - build on windows failed: 'make: execvp: uname: File or path name too long'
356 * ``ZEP-1302`` - ENC28J60 fails with rx/tx of long frames
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | index.rst | 31 two ways. A stable and long-lived API :ref:`sensor-fetch-and-get`, or a newer
|
| D | read_and_decode.rst | 54 * Far less likely triggers are missed due to long held interrupt masks from
|
| /Zephyr-latest/cmake/sca/eclair/ECL/ |
| D | toolchain.ecl | 82 …merations, and Bit-Fields\" of "GCC_MANUAL". Other integer types, such as long int, and enumerated…
|
| /Zephyr-latest/samples/drivers/soc_flash_nrf/ |
| D | README.rst | 23 The sample will be built for any SoC with internal storage, as long as
|
| /Zephyr-latest/doc/services/ |
| D | formatted_output.rst | 63 formatted from such package as long as there is access to read-only string
72 from such package as long as non read-only strings are still valid and read-only
|
| /Zephyr-latest/tests/benchmarks/thread_metric/ |
| D | thread_metric_readme.txt | 176 int tm_queue_send(int queue_id, unsigned long *message_ptr);
181 int tm_queue_receive(int queue_id, unsigned long *message_ptr);
|
| /Zephyr-latest/subsys/debug/ |
| D | Kconfig | 59 The thread analysis takes quite a long time.
65 the interrupts for a long time - long enough to disconnect when
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_8.rst | 38 Note that file handles will remain open for consecutive requests (as long as
167 Note that file handles will remain open for consecutive requests (as long as
171 requests (as long as an idle timeout has not been reached and another transport
|
| /Zephyr-latest/doc/services/ipc/ipc_service/backends/ |
| D | ipc_service_icbmsg.rst | 27 …During this time other threads are not blocked in any way as long as there are enough free blocks …
31 * The receiver can hold the data as long as desired.
32 Again, other threads are not blocked as long as there are enough free blocks for them.
|
| /Zephyr-latest/cmake/modules/ |
| D | FindDeprecated.cmake | 18 # such code can easily be around for a long time, so therefore such code should
|
| /Zephyr-latest/doc/services/portability/posix/conformance/ |
| D | index.rst | 27 However, we may add implementations that simply fail with ENOSYS as long as the functional
|
| /Zephyr-latest/doc/services/input/ |
| D | index.rst | 102 for short and long press.
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig | 8 bool "Dedicated workqueue for long-running tasks."
11 Adds an API for a workqueue dedicated to long-running tasks.
31 Init priority level to setup the long workqueue.
192 which will not consume additional resources, but may take a long time,
233 thread for too long.
871 long (excluding NULL termination).
877 Bluetooth device name. Name can be up to 248 bytes long (excluding
|
| /Zephyr-latest/doc/project/ |
| D | proposals.rst | 105 Items labeled as ``features`` are short or long term release items that shall
|
| /Zephyr-latest/boards/renesas/ek_ra4w1/doc/ |
| D | index.rst | 12 has full function support for Bluetooth 5.0 Low Energy long-range and mesh networking, and provides
|
| /Zephyr-latest/doc/build/version/ |
| D | index.rst | 195 No additional configuration needs to be done to the target application so long as it is configured
|
| /Zephyr-latest/share/zephyr-package/cmake/ |
| D | ZephyrConfigVersion.cmake | 25 # For now, Zephyr is capable to find the right base on all older versions as long as they define
|
123456789
