Home
last modified time | relevance | path

Searched full:introduce (Results 1 – 25 of 62) sorted by relevance

123

/Zephyr-latest/doc/build/dts/
Dintro.rst11 The following pages introduce general devicetree concepts and how they apply to
Dbindings.rst15 These pages introduce bindings, describe what they do, note where they are
Dphandles.rst192 enforced. To answer this question, we'll need to introduce a concept called
/Zephyr-latest/soc/intel/intel_adsp/
DKconfig.defconfig20 # console can't handle the amount of data coming from many tests, so introduce
/Zephyr-latest/lib/posix/options/
DKconfig.barrier33 On such systems, say Y here to introduce explicit serialization
DKconfig.toolchain9 # Use these features with caution as doing so might introduce unwanted, unexpected, or undefined
/Zephyr-latest/dts/bindings/display/
Drenesas,smartbond-display.yaml33 is stored into external storage mediums, e.g. PSRAM, that introduce comparable delays.
/Zephyr-latest/dts/bindings/mipi-dbi/
Drenesas,smartbond-mipi-dbi.yaml43 is stored into external storage mediums, e.g. PSRAM, that introduce comparable delays.
/Zephyr-latest/dts/bindings/input/
Dst,stmpe811.yaml89 Higher values result in more filtering of noise, but also introduce
/Zephyr-latest/include/zephyr/
Dfatal.h43 * weak symbol so that applications may introduce their own policy.
/Zephyr-latest/include/zephyr/net/
Dnet_linkaddr.h46 * into a uint8_t variable, so please do not introduce any values > 255 in
/Zephyr-latest/arch/nios2/core/
Dfatal.c23 * entry. We may want to introduce a config option to save and in z_nios2_fatal_error()
/Zephyr-latest/doc/develop/api/
Dapi_lifecycle.rst8 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/
Dindex.rst75 or introduce different signing mechanisms. By default with MCUboot enabled, signing is setup by
/Zephyr-latest/drivers/interrupt_controller/
Dintc_ite_it8xxx2_v2.c55 * so we introduce workaround here. in ite_intc_save_and_disable_interrupts()
Dintc_ite_it8xxx2.c78 * so we introduce workaround here. in ite_intc_save_and_disable_interrupts()
/Zephyr-latest/doc/releases/
Drelease-notes-1.10.rst48 * 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
Drelease-notes-1.12.rst52 * 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/
Dcommon.h145 * fixed via possibly #4174, we introduce this hack -- which will
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_backporting.rst159 As an MCUmgr maintainer, you may not be able to merge the ``west.yml`` update, to introduce the fix…
/Zephyr-latest/doc/services/pm/
Ddevice_runtime.rst103 The synchronous model is as simple as it gets. However, it may introduce
/Zephyr-latest/tests/net/promiscuous/src/
Dmain.c181 /* As native_sim board will introduce another ethernet in iface_cb()
/Zephyr-latest/doc/contribute/
Dexternal.rst62 - Is this the most optimal way to introduce the functionality to the project?
Dcontributor_expectations.rst64 #. Introduce the new APIs, including shared devicetree bindings
/Zephyr-latest/arch/xtensa/core/
DREADME_MMU.txt6 to introduce the architecture at an overview/tutorial level, and to

123