Searched refs:their (Results 301 – 325 of 351) sorted by relevance
1...<<1112131415
| /Zephyr-latest/doc/kernel/services/scheduling/ |
| D | index.rst | 48 their static priorities and deadlines are equal. The routine
|
| /Zephyr-latest/cmake/linker/ |
| D | linker_script_common.cmake | 563 # Each linker must implement their own <type>_to_string() functions to
|
| /Zephyr-latest/boards/snps/nsim/arc_classic/doc/ |
| D | index.rst | 243 avoid intermixing their output. For the MDB debugger simply use GUI mode.
|
| /Zephyr-latest/doc/services/pm/ |
| D | device.rst | 84 care of suspending devices following their initialization order, ensuring that
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_1.rst | 64 with their current state.
|
| D | smp_group_0.rst | 765 | | their natural ascending index order, not the order of |
|
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | Kconfig.tfm | 321 to their own checkout of this library, or set to DOWNLOAD to allow
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 207 in this case, there are two released versions of Zephyr installed at their own workspaces.
|
| /Zephyr-latest/arch/ |
| D | Kconfig | 158 # POSIX arch based targets get their memory cleared on entry by the host OS
1005 The developers can still disable the FP sharing mode in their
|
| /Zephyr-latest/kernel/ |
| D | Kconfig | 148 architecture and want to make their own decisions about how
624 do not have support for atomic operations in their instruction
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | float.rst | 212 make the FPU state "dirty" during their most recent scheduling slot before
|
| /Zephyr-latest/doc/build/dts/ |
| D | macros.bnf | 304 ; - with "enum:" in their bindings
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | shell.rst | 522 * Monitor the newly provisioned nodes and their addresses (``mesh cdb show``).
792 Subscription the model to a group address. Models only receive messages sent to their
816 Subscribe the model to a virtual address. Models only receive messages sent to their unicast
850 messages sent to their unicast address or a group or virtual address they subscribe to.
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-2.2.rst | 134 drivers will have to update their DTS board files.
701 their own standalone repositories.
896 * :github:`22177` - Adafruit M0 boards are not set up to correctly flash in their code partitions
|
| D | release-notes-2.5.rst | 92 :c:func:`fs_file_t_init` before their first use.
95 :c:func:`fs_dir_t_init` before their first use.
149 look at porting their logic, or perhaps at the k_mem_slab utility.
889 their own standalone repositories.
1727 * :github:`27716` - Bluetooth: Mesh: Devices relay their own messages (even with relay disabled!)
|
| D | release-notes-2.7.rst | 794 * Various bindings had incorrect vendor prefixes in their :ref:`compatible
826 Out of tree users of these bindings will need to update their
957 can override them. Platforms can have their own way to
958 set/release constraints in their drivers that are not part of
994 their own standalone repositories.
|
| D | release-notes-3.2.rst | 83 their context more clear:
488 that allows users to list, fetch and delete binary blobs from their
608 * Drivers are enabled by default based on their devicetree hardware declarations.
974 * All devicetree macros now recursively expand their arguments. This means
1208 * Various peripheral bindings have had their SoC-specific
1382 * Removed the need to manually register emulators in their init function (automatically done).
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | board_porting.rst | 277 boards such as the boards names, their SoCs, and variants.
635 and their drivers disabled by default.
|
| /Zephyr-latest/doc/services/zbus/ |
| D | index.rst | 135 control the channel in so many different ways claiming the channel, developers can add their
531 may want to piggy-back on their channels. The following code defines and initializes a :dfn:`hard
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | hci.txt | 830 identified by their corresponding Handle in case Advertising Extensions are
953 identified by their corresponding Handle in case Advertising Extensions are
|
| /Zephyr-latest/doc/ |
| D | zephyr.doxyfile.in | 389 # classes, or namespaces to their corresponding documentation. Such a link can
487 # cache is used to resolve symbols given their name and scope. Since this can be
646 # their full class and namespace scopes in the documentation. If set to YES, the
719 # appear in their defined order.
900 # are documented, but have no documentation for their parameters or return
2213 # replacements, missing definitions are set to their default value.
2744 # collaboration graphs will show the relations between templates and their
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | mailboxes.rst | 317 receive queue. The threads are sorted according to their priority;
|
| /Zephyr-latest/doc/develop/flash_debug/ |
| D | host-tools.rst | 281 you would like to single step from the start of their application, you
|
| /Zephyr-latest/doc/hardware/pinctrl/ |
| D | index.rst | 386 option is better for their devices. However, the following guidelines should be
|
| /Zephyr-latest/boards/espressif/esp_wrover_kit/doc/ |
| D | index.rst | 31 The block diagram below shows the main components of ESP-WROVER-KIT and their interconnections.
|
1...<<1112131415
