Searched full:introduce (Results 1 – 25 of 62) sorted by relevance
123
/Zephyr-latest/doc/build/dts/ |
D | intro.rst | 11 The following pages introduce general devicetree concepts and how they apply to
|
D | bindings.rst | 15 These pages introduce bindings, describe what they do, note where they are
|
D | phandles.rst | 192 enforced. To answer this question, we'll need to introduce a concept called
|
/Zephyr-latest/soc/intel/intel_adsp/ |
D | Kconfig.defconfig | 20 # console can't handle the amount of data coming from many tests, so introduce
|
/Zephyr-latest/lib/posix/options/ |
D | Kconfig.barrier | 33 On such systems, say Y here to introduce explicit serialization
|
D | Kconfig.toolchain | 9 # Use these features with caution as doing so might introduce unwanted, unexpected, or undefined
|
/Zephyr-latest/dts/bindings/display/ |
D | renesas,smartbond-display.yaml | 33 is stored into external storage mediums, e.g. PSRAM, that introduce comparable delays.
|
/Zephyr-latest/dts/bindings/mipi-dbi/ |
D | renesas,smartbond-mipi-dbi.yaml | 43 is stored into external storage mediums, e.g. PSRAM, that introduce comparable delays.
|
/Zephyr-latest/dts/bindings/input/ |
D | st,stmpe811.yaml | 89 Higher values result in more filtering of noise, but also introduce
|
/Zephyr-latest/include/zephyr/ |
D | fatal.h | 43 * weak symbol so that applications may introduce their own policy.
|
/Zephyr-latest/include/zephyr/net/ |
D | net_linkaddr.h | 46 * into a uint8_t variable, so please do not introduce any values > 255 in
|
/Zephyr-latest/arch/nios2/core/ |
D | fatal.c | 23 * entry. We may want to introduce a config option to save and in z_nios2_fatal_error()
|
/Zephyr-latest/doc/develop/api/ |
D | api_lifecycle.rst | 8 maintaining and extending Zephyr's APIs need to be able to introduce 168 whether to introduce both the RFC and the Pull Request at the same time or to
|
/Zephyr-latest/doc/build/signing/ |
D | index.rst | 75 or introduce different signing mechanisms. By default with MCUboot enabled, signing is setup by
|
/Zephyr-latest/drivers/interrupt_controller/ |
D | intc_ite_it8xxx2_v2.c | 55 * so we introduce workaround here. in ite_intc_save_and_disable_interrupts()
|
D | intc_ite_it8xxx2.c | 78 * so we introduce workaround here. in ite_intc_save_and_disable_interrupts()
|
/Zephyr-latest/doc/releases/ |
D | release-notes-1.10.rst | 48 * Introduce object validation mechanism: All system calls made from userspace, 95 * Introduce mcux ccm driver 96 * Introduce mcux igpio shim driver 138 either simple one-to-one translations of KBuild features or introduce 287 * :github:`3290` - introduce shared metadata for boards, samples and tests
|
D | release-notes-1.12.rst | 52 * kernel: introduce initial stack randomization 126 * dma: Introduce Intel CAVS DMA 132 * i2s: Introduce CAVS I2S 134 * interrupts: introduce CAVS interrupt logic 135 * interrupts: Introduce Designware interrupt controller 234 * scripts: west: introduce common runner configuration
|
/Zephyr-latest/include/zephyr/toolchain/ |
D | common.h | 145 * fixed via possibly #4174, we introduce this hack -- which will
|
/Zephyr-latest/doc/services/device_mgmt/ |
D | mcumgr_backporting.rst | 159 As an MCUmgr maintainer, you may not be able to merge the ``west.yml`` update, to introduce the fix…
|
/Zephyr-latest/doc/services/pm/ |
D | device_runtime.rst | 103 The synchronous model is as simple as it gets. However, it may introduce
|
/Zephyr-latest/tests/net/promiscuous/src/ |
D | main.c | 181 /* As native_sim board will introduce another ethernet in iface_cb()
|
/Zephyr-latest/doc/contribute/ |
D | external.rst | 62 - Is this the most optimal way to introduce the functionality to the project?
|
D | contributor_expectations.rst | 64 #. Introduce the new APIs, including shared devicetree bindings
|
/Zephyr-latest/arch/xtensa/core/ |
D | README_MMU.txt | 6 to introduce the architecture at an overview/tutorial level, and to
|
123