Searched refs:been (Results 201 – 225 of 490) sorted by relevance
12345678910>>...20
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | fetch_and_get.rst | 16 has been obtained and stored into the driver instance's private data.
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-2.4.rst | 58 * The ``<sys/util.h>`` header has been promoted to a documented API with
70 :c:type:`uart_irq_callback_t` has been removed. :c:func:`uart_callback_set`,
72 user code have been modified accordingly.
76 signature has been generalized through the addition of dma_callback_t.
77 'callback_arg' argument has been renamed to 'user_data. All user code have
78 been modified accordingly.
83 been modified accordingly. The context argument has been renamed to user_data
84 and all drivers have been modified against it as well.
103 * The ``_gatt_`` and ``_GATT_`` infixes have been removed for the HRS, DIS
108 been changed to always pass the original pointer of attributes along with its
[all …]
|
| /Zephyr-latest/boards/arm/mps3/doc/ |
| D | index.rst | 27 The FVPs have been selected for simulation since they provide access to the
116 has been tested with version 11.24.13 (Jan 4 2024).
173 has been tested with version 11.24.13 (Jan 4 2024).
|
| /Zephyr-latest/share/sysbuild/cmake/modules/ |
| D | sysbuild_kconfig.cmake | 67 # We only want to set this in cache it has been defined and is not already there.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | ptp.rst | 129 The stack has been informally tested using the
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | usbnet_setup.rst | 67 been assigned to the board. We can use either IPv4 or IPv6 for network
|
| /Zephyr-latest/boards/holyiot/yj16019/doc/ |
| D | index.rst | 60 Other hardware features have not been enabled yet for this board.
|
| /Zephyr-latest/modules/ |
| D | Kconfig | 17 build time to reflect that the build might have been tainted by them.
|
| /Zephyr-latest/boards/adafruit/feather_stm32f405/doc/ |
| D | index.rst | 51 Other hardware features have not been enabled yet for this board.
|
| /Zephyr-latest/boards/nordic/nrf51dongle/doc/ |
| D | index.rst | 77 Other hardware features have not been enabled yet for this board.
|
| /Zephyr-latest/boards/olimex/stm32_h405/doc/ |
| D | index.rst | 44 Other hardware features have not been enabled yet for this board.
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | workqueue.rst | 21 * A **queue** of work items that have been added, but not yet processed.
46 * The ability to wait until a work item has completed or a queue has been
125 A pending work item *must not* be altered until the item has been processed
393 with work items after they've been submitted. :c:func:`k_work_flush()`,
395 can be invoked from thread context to wait until the requested state has been
451 Note that submitting from the work handler can fail if the work item had been
482 Many race conditions have been present in Zephyr code because the results of
|
| /Zephyr-latest/doc/kernel/services/scheduling/ |
| D | index.rst | 40 exist, the scheduler chooses the one that has been waiting longest.
54 at any time unless interrupts have been masked. This applies to both
328 system completely. To prevent this, k_cpu_atomic_idle() should have been used,
350 * go to next loop iteration (the semaphore might have been given
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 158 and tracing in hand, it can now be verified whether the functionality has been tested and
189 already been implemented in the Zephyr project and need to be verified by the Safety Committee /
196 approach has been pursued in the Zephyr project from the beginning with its layered architecture.
270 circumstances, specifically when something has been identified during the certification process
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_1.rst | 99 Below definition of the response contains "image" field that has been marked
187 | "confirmed" | true if image has been confirmed; this field does not have to be |
327 is started, if the device has rebooted or if a packet has been lost. If this
520 image has been marked for next boot already and may not be erased.
|
| /Zephyr-latest/scripts/net/ |
| D | README.txt | 10 'net-tools' Docker container has been created, see the first bullet point
|
| /Zephyr-latest/doc/build/dts/ |
| D | dt-vs-kconfig.rst | 49 instance of a driver (that is itself enabled by Kconfig) have been
|
| /Zephyr-latest/samples/boards/nordic/dynamic_pinctrl/ |
| D | README.rst | 29 associated pins has not been initialized yet. Therefore, pay attention to the
|
| /Zephyr-latest/boards/contextualelectronics/abc/doc/ |
| D | index.rst | 69 Other hardware features have not been enabled yet for this board.
|
| /Zephyr-latest/boards/mikroe/clicker_2/doc/ |
| D | mikroe_clicker_2.rst | 45 Other hardware features have not been enabled yet for this board.
|
| /Zephyr-latest/lib/libc/ |
| D | Kconfig | 150 the C library even though it would not have been enabled
|
| /Zephyr-latest/doc/develop/api/ |
| D | terminology.rst | 21 if the function can be safely called before the kernel has been fully
151 been started.
|
| /Zephyr-latest/doc/develop/west/ |
| D | troubleshooting.rst | 56 :envvar:`PATH`. (This :envvar:`PATH` change should have been done for you when
102 Neither macOS nor Windows users have reported this issue. There have been no
|
| /Zephyr-latest/doc/services/binary_descriptors/ |
| D | index.rst | 123 #. RAM - assuming the descriptors have been copied to RAM (e.g. by a bootloader), they
148 The rest of the API is agnostic to where the data is. After the handle has been initialized,
|
| /Zephyr-latest/doc/services/crypto/ |
| D | psa_crypto.rst | 88 has been generated inside a secure key store. The API provides access
93 provisioning process, or once they have been deployed to the
|
12345678910>>...20
