Searched refs:their (Results 126 – 150 of 360) sorted by relevance
12345678910>>...15
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.sam_gmac | 35 routed to appropriate queues based on their priority.
|
| /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/develop/west/ |
| D | troubleshooting.rst | 18 The output includes Git commands run by west and their outputs. Look for
120 library. Some distributions remove this module from their base Python 3
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu.rst | 53 Target nodes and their firmware, and will control (and initiate) all firmware updates. The
98 and their designated firmware image index to the Distributor. Next, it tells the Distributor to
102 their status and new firmware IDs.
307 check and prepares their BLOB Transfer Server model for the transfer, before sending a status
344 message before calling their application's ``apply`` callback.
|
| /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
141 * Responsibility to triage static analysis issues in their code area.
230 * Responsibility to merge all contributions regardless of their
390 only by their own organisation. To be able to merge such changes, at least
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.cortex_m_systick | 102 Some SoCs provide one or more low-power mode which, as part of their
|
| /Zephyr-latest/boards/wiznet/w5500_evb_pico2/doc/ |
| D | index.rst | 11 their SWD interface, using an external adapter.
|
| /Zephyr-latest/boards/st/stm32h735g_disco/doc/ |
| D | index.rst | 15 their application development by an evaluation of all the peripherals (such as
|
| /Zephyr-latest/doc/contribute/ |
| D | reviewer_expectations.rst | 18 - Reviewers shall strive to advance the PR to a mergeable state with their
|
| D | contributor_expectations.rst | 101 - The PR description must include a summary of the changes and their rationales.
284 reviewers a minimum of 1 business day to respond and revisit their initial
288 any reviews in the PR and should notify the reviewer about their review being
|
| /Zephyr-latest/doc/services/resource_management/ |
| D | index.rst | 57 responsible for recording whether their requests were accepted, and for
|
| /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/cmake/modules/ |
| D | shields.cmake | 104 # Add board-specific .conf and .overlay files to their
|
| /Zephyr-latest/dts/bindings/ |
| D | binding-types.txt | 7 # file) to their descriptions and provides a definition for each acronym used.
|
| /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:
|
| /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/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/doc/releases/ |
| D | release-notes-4.2.rst | 23 Does the thing require the user to change their application? Put it on the
|
| /Zephyr-latest/boards/st/stm32h750b_dk/doc/ |
| D | index.rst | 15 their application development by an evaluation of all the peripherals (such as
|
| /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/doc/kernel/services/data_passing/ |
| D | stacks.rst | 92 can create a pool of data structures by saving their memory addresses
|
| /Zephyr-latest/samples/modules/chre/ |
| D | README.rst | 61 community. These should each have their own Kconfig to enable them and set the appropriate
|
12345678910>>...15
