Searched refs:their (Results 101 – 125 of 351) sorted by relevance
12345678910>>...15
| /Zephyr-latest/boards/native/doc/ |
| D | bsim_boards_design.rst | 26 can be found in their respective documentation.
63 peripherals, and their execution is independent of the host load, or timing.
97 it is possible to test the components interactions and their integration.
101 audio over their radio link, and how they interact with a mobile phone.
216 a general introduction to the babblesim HW models and their scheduling are provided.
239 together with an API for components that use it to inform about their events
|
| /Zephyr-latest/boards/shields/ls0xx_generic/doc/ |
| D | index.rst | 33 define ``extcomin-gpios`` and implement their preferred method in
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-shell.rst | 72 * List the available modules and their current logging level
|
| /Zephyr-latest/doc/build/dts/ |
| D | zephyr-user-node.rst | 8 you can put essentially arbitrary properties inside it and retrieve their
|
| D | dt-vs-kconfig.rst | 32 their boot-time configuration is described in devicetree.
|
| /Zephyr-latest/doc/develop/sca/ |
| D | codechecker.rst | 36 CodeChecker uses different command steps, each with their respective configuration
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 25 with their own group of threads and private data structures, which are
54 - On MPU systems, threads may only access their own stack buffer.
152 driver other than their own thread object. Such access must be granted by
|
| /Zephyr-latest/modules/openthread/ |
| D | Kconfig.thread | 127 To allow end devices (EDs) in a Thread network to inform their
135 better parent router than their current one—while still attached
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 58 help prevent security violations and limit their impact:
88 of permissions in the system required to perform their task. This
99 easy to use by the developers in order to ensure their usage and the
243 system (based on their general understanding of security), and if so,
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | nothread.rst | 82 threading is disabled, but are within scope based on their subsystem, or
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | fetch_and_get.rst | 63 * Driver dedicated threads *do* get their own priority typically which lets you
|
| /Zephyr-latest/boards/sc/scobc_module1/doc/ |
| D | index.rst | 16 their mission.
|
| /Zephyr-latest/samples/subsys/display/lvgl/ |
| D | README.rst | 25 can be used to navigate between widgets and edit their values. If the
|
| /Zephyr-latest/boards/shields/x_nucleo_eeprma2/ |
| D | x_nucleo_eeprma2.overlay | 71 * and are connected to their respective arduino pins via a normally
|
| /Zephyr-latest/lib/libc/common/ |
| D | Kconfig | 75 regions be sized to a power of two and aligned to their size,
|
| /Zephyr-latest/boards/nxp/mimxrt685_evk/ |
| D | mimxrt685_evk-pinctrl.dtsi | 156 * through 5B for differential input on their respective ADC channel.
|
| /Zephyr-latest/doc/contribute/ |
| D | contributor_expectations.rst | 96 - The PR description must include a summary of the changes and their rationales.
225 reviewers a minimum of 1 business day to respond and revisit their initial
229 any reviews in the PR and should notify the reviewer about their review being
281 - Reviewers shall strive to advance the PR to a mergeable state with their
|
| /Zephyr-latest/doc/kernel/services/ |
| D | index.rst | 54 The following table summarizes their high-level features.
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | dma.rst | 50 A diagram, showing those expected possible state transitions and their API calls is provided here
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf54l15bsim.rst | 85 * All RAM, flash and peripherals are in principle accessible from all SW. Peripherals with their
|
| /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.
306 check and prepares their BLOB Transfer Server model for the transfer, before sending a status
343 message before calling their application's ``apply`` callback.
|
| /Zephyr-latest/cmake/modules/ |
| D | hwm_v2.cmake | 38 # 'SOC_ROOT' and 'ARCH_ROOT' are prioritized lists of directories where their
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.sam_gmac | 36 routed to appropriate queues based on their priority.
|
| /Zephyr-latest/boards/mikroe/clicker_2/doc/ |
| D | mikroe_clicker_2.rst | 53 The two mikroBUS interfaces are aliased in the device tree so that their
|
| /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
|
12345678910>>...15
