Searched refs:their (Results 126 – 150 of 351) sorted by relevance
12345678910>>...15
| /Zephyr-latest/doc/security/ |
| D | reporting.rst | 152 mailing list describing known embargoed issues, and their backport
204 - Maintainers will have access to all information within their domain
|
| /Zephyr-latest/doc/project/ |
| D | documentation.rst | 47 reports and using their name and identifier is the best way to identify them
|
| D | project_roles.rst | 56 Contributors are not allowed to assign reviewers to their own pull requests. An
131 * Responsibility to triage static analysis issues in their code area.
220 * Responsibility to merge all contributions regardless of their
379 only by their own organisation. To be able to merge such changes, at least
|
| /Zephyr-latest/cmake/modules/ |
| D | shields.cmake | 104 # Add board-specific .conf and .overlay files to their
|
| /Zephyr-latest/doc/services/resource_management/ |
| D | index.rst | 57 responsible for recording whether their requests were accepted, and for
|
| /Zephyr-latest/doc/develop/tools/ |
| D | vscode.rst | 74 guide does not cover them yet, you may refer to their documentation to set them up:
|
| D | coccinelle.rst | 88 * ``context`` highlights lines of interest and their context in a
289 SmPL patches can have their own requirements for options passed
480 ``context`` highlights lines of interest and their context
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.obj_core | 9 participating kernel objects and their respective types together
|
| /Zephyr-latest/doc/services/pm/ |
| D | device_runtime.rst | 85 efficient to keep parent devices active when their children are used, since
87 Until this feature is added, devices can manually *get* or *put* their
|
| /Zephyr-latest/samples/userspace/prod_consumer/ |
| D | README.rst | 16 - Multiple logical applications, each with their own memory domain
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | stacks.rst | 92 can create a pool of data structures by saving their memory addresses
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | read_and_decode.rst | 85 asynchronously for all sensors and their channels. When each read completes we
|
| /Zephyr-latest/samples/subsys/llext/shell_loader/ |
| D | README.rst | 41 list :List loaded extensions and their size in memory
|
| /Zephyr-latest/samples/modules/chre/ |
| D | README.rst | 61 community. These should each have their own Kconfig to enable them and set the appropriate
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.profile | 26 This choice is intended to help users select the correct POSIX profile for their
|
| /Zephyr-latest/boards/st/stm32373c_eval/doc/ |
| D | index.rst | 7 …r and receiver, EEPROM, touch slider, temperature sensor, etc.) and develop their own applications.
|
| /Zephyr-latest/lib/heap/ |
| D | Kconfig | 112 their size albeit with some overhead in code size and execution.
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | generation.rst | 26 their respective websites.
33 code source tree near their specific component (such as ``/samples`` and
|
| /Zephyr-latest/doc/hardware/peripherals/can/ |
| D | shell.rst | 51 support tab-completion of their arguments.
54 All of the CAN shell subcommands take the name of a CAN controller as their first argument, which
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm_cortex_m.rst | 102 …ecture variants, thread stacks are additionally required to align with a value equal to their size,
413 no memory corruption occurs when supervisor threads overflow their stack memory
543 The developers can still disable the FP sharing mode in their
571 normally occupy a specific area in the flash denoted as their *code partition*.
579 hardware registers and peripherals are initialized in their reset values. Enabling
591 Baseline Cortex-M platforms without VTOR register might not be able to relocate their
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.6.rst | 42 can specify their own custom system heap size requirements by specifying Kconfig options with
256 along with their initializer macros.
269 in their receive callback functions as needed.
276 is enabled, applications can still filter between Data and RTR frames in their receive callback
522 ``<zephyr/bluetooth/audio/audio.h>`` and have the ``LC3`` part of their names replaced by a
|
| D | migration-guide-3.7.rst | 83 their project config file. (:github:`73067`)
101 The ``_MAC`` and ``_ENABLED`` parts have been removed from their names. (:github:`73267`)
264 been removed, users should remove this property from their devicetree if it is present.
544 drop this property from their devicetree, and set orientation at runtime
656 has been removed, users should remove this property from their devicetree if it is present.
689 rather the UART HCI drivers select their UART by looking for the parent devicetree node of the
695 choice, rather they can now be enabled and disabled independently, mostly based on their
|
| /Zephyr-latest/samples/subsys/zbus/priority_boost/ |
| D | README.rst | 122 The developer must enable the priority boost and properly attach all the observers to their threads.
|
| /Zephyr-latest/boards/weact/stm32g431_core/doc/ |
| D | index.rst | 11 and CC2 need to be disconnected from their pull-down resistors and be connected to PB6 and
|
| /Zephyr-latest/cmake/flash/ |
| D | CMakeLists.txt | 141 # Available runners and their arguments are configured in board.cmake
|
12345678910>>...15
