Home
last modified time | relevance | path

Searched refs:provide (Results 26 – 50 of 442) sorted by relevance

12345678910>>...18

/Zephyr-latest/drivers/serial/
DKconfig.it8xxx212 provide a power management callback, so create driver
/Zephyr-latest/lib/posix/options/
DKconfig.procN25 Select 'y' here and Zephyr will provide an alias for getpid() as _getpid().
DKconfig.c_lib_ext8 Select 'y' here and Zephyr will provide an implementation of the POSIX_C_LIB_EXT Option
/Zephyr-latest/samples/net/openthread/shell/
DREADME.rst16 Verify that the board and chip you are targeting provide IEEE 802.15.4 support.
/Zephyr-latest/samples/drivers/adc/adc_sequence/
DREADME.rst25 oversampling setting (if used). It is also needed to provide an alias ``adc0`` for the
43 and provide a corresponding devicetree overlay.
/Zephyr-latest/doc/hardware/peripherals/
Dcoredump.rst14 of the desired size and provide an API to register a callback function to fill that
/Zephyr-latest/samples/sensor/adc_cmp_npcx/
DREADME.rst20 Build the application for the :zephyr:board:`npcx9m6f_evb` board, and provide voltage
/Zephyr-latest/doc/build/dts/
Dbindings.rst7 is a relatively unstructured format. *Devicetree bindings* provide the other
Dindex.rst10 - to provide that hardware's initial configuration
/Zephyr-latest/samples/net/promiscuous_mode/
DREADME.rst14 The application will also provide a shell so that user can enable
/Zephyr-latest/cmake/
Dtarget_toolchain_flags.cmake27 # Load the compile features file which will provide compile features lists for
34 # They purely provide an overview as well as a starting point for supporting
/Zephyr-latest/doc/hardware/porting/
Dshields.rst42 to provide a device nodelabel is the form <device>_<shield>, for instance:
74 software compatibility, boards must also provide a configuration matching
129 possible to provide multiple version of the shields description:
146 You can also provide a board-specific configuration to a specific shield
166 compatible. Boards that provide the header must map the header pins
/Zephyr-latest/samples/drivers/jesd216/boards/
Dnrf52840dk_nrf52840_spi.overlay14 * to provide quad-spi feature. In individual specifications each of the spi
/Zephyr-latest/tests/drivers/clock_control/stm32_clock_configuration/stm32_common_devices/boards/
Df0_i2c1_hsi.overlay45 * Aim of this part is to provide a base working clock config
Df3_i2c1_hsi.overlay45 * Aim of this part is to provide a base working clock config
Df4_i2s2_pll.overlay48 * Aim of this part is to provide a base working clock config
Dg0_i2c1_hsi_lptim1_lse_adc1_pllp.overlay38 * Aim of this part is to provide a base working clock config
Dg4_i2c1_hsi_adc1_pllp.overlay38 * Aim of this part is to provide a base working clock config
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dindex.rst16 attempts to provide a uniform interface to them.
63 * SHOULD provide the ability to get and set channel scale if supported by the
65 * SHOULD provide the ability to get and set channel sampling rate if supported
/Zephyr-latest/include/zephyr/drivers/misc/
DREADME13 resistive touch controller. The graphic controller does not provide frame
/Zephyr-latest/.github/ISSUE_TEMPLATE/
D008_bin-blobs.md26 the functionality that the blob(s) provide, to the largest extent possible
/Zephyr-latest/drivers/audio/
DKconfig.dmic_mcux22 API should provide at least one more buffer than this value, since
/Zephyr-latest/samples/
Dsample_definition_and_criteria.rst21 * The primary purpose of a sample is to provide a reference to the user.
27 * If a sample can provide output that can be verified, then output should be evaluated against
85 3. A sample should provide sufficient coverage of a subsystem, feature, or module.
/Zephyr-latest/doc/services/debugging/
Dsymtab.rst17 file and call :c:func:`symtab_get`. For now, we only provide :c:func:`symtab_find_symbol_name`
/Zephyr-latest/samples/net/wifi/shell/
DREADME.rst18 Verify the board and chip you are targeting provide Wi-Fi support.

12345678910>>...18