Home
last modified time | relevance | path

Searched refs:needs (Results 51 – 75 of 523) sorted by relevance

12345678910>>...21

/Zephyr-latest/samples/sensor/lsm6dso_i2c_on_i3c/
DREADME.rst60 A LSM6DSO sensor needs to be connected to this header. For example,
61 the evaluation board STEVAL-MKI196V1 can be used. This needs to be
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_callbacks.rst205 (which can be modified by handlers). If no data needs to be passed back,
292 :kconfig:option:`CONFIG_MCUMGR_SMP_COMMAND_STATUS_HOOKS` needs to be set.
296 the action or false to deny, a MCUmgr result code needs to be returned,
300 error). :kconfig:option:`CONFIG_MCUMGR_GRP_IMG_STATUS_HOOKS` needs to be
310 :kconfig:option:`CONFIG_MCUMGR_GRP_IMG_STATUS_HOOKS` needs to be set.
314 allow the action or false to deny, a MCUmgr result code needs to be
318 error). :kconfig:option:`CONFIG_MCUMGR_GRP_IMG_UPLOAD_CHECK_HOOK` needs to
322 true to allow the action or false to deny, a MCUmgr result code needs to be
326 error). :kconfig:option:`CONFIG_MCUMGR_SMP_COMMAND_STATUS_HOOKS` needs to
/Zephyr-latest/drivers/ieee802154/
DKconfig.kw41z24 The value depends on your debugging needs. This generates an encoded
/Zephyr-latest/soc/ti/simplelink/cc13x2_cc26x2/
DKconfig.defconfig10 # Note that when using the RTC as system clock, this needs to be 32768
/Zephyr-latest/drivers/dma/
DKconfig.intel_adsp_gpdma19 Hidden option to indicate that the driver needs to request
DKconfig.nxp_edma21 This value needs to match one of the possible
/Zephyr-latest/doc/services/retention/
Dblinfo.rst15 To use the bootloader information subsystem, a retention area needs to be
54 Note that this configuration needs to be applied on both the bootloader
61 Once the above devicetree configuration is applied, MCUboot needs to be
/Zephyr-latest/drivers/sdhc/
DKconfig.imx31 # USDHC DMA needs 32 bit aligned buffers
/Zephyr-latest/boards/shields/wnc_m14a2a/boards/
Dnrf52840dk_nrf52840.overlay30 * headers. It needs to be defined individually.
/Zephyr-latest/cmake/toolchain/xt-clang/
Dgeneric.cmake15 # lengthens the CMake phase of build, especially when xt-clang needs to
/Zephyr-latest/soc/nxp/imxrt/imxrt6xx/
DKconfig.defconfig43 # MBEDTLS CTR_DRBG code path needs extra stack space for initialization than
/Zephyr-latest/samples/subsys/fs/fs_sample/boards/
Dnrf52840dk_nrf52840.overlay7 /* Because FAT FS needs at least 64kiB partition and default
/Zephyr-latest/samples/sysbuild/hello_world/
DREADME.rst22 This sample needs to be built with Sysbuild by using the ``--sysbuild`` option.
23 The remote board needs to be specified using ``SB_CONFIG_REMOTE_BOARD``. Some
/Zephyr-latest/samples/sensor/lps22hh_i3c/
DREADME.rst69 A LPS22HH sensor needs to be connected to this header. For example,
70 the evaluation board STEVAL-MKI192V1 can be used. This needs to be
/Zephyr-latest/samples/sensor/mcux_lpcmp/
DREADME.rst14 voltage of the DAC is set to 0 (for the specific chip, the user needs to
18 The positive input port is set to 0, the user needs to check the reference
/Zephyr-latest/samples/boards/nxp/adsp/number_crunching/
DREADME.rst13 To use this sample, with an out of tree library, one needs to define an environment variable
15 In that location, one needs to have a ``CMakeLists.txt`` that defines:
37 If one wants to include a new backend it needs to create a new wrapper for that library or backend.
42 CMSIS-DSP is an optional module and needs to be added explicitly to your Zephyr workspace:
/Zephyr-latest/drivers/interrupt_controller/
DKconfig.clic25 to select the behavior for each interrupt. The CLIC driver needs to
/Zephyr-latest/doc/connectivity/networking/api/
Dethernet_mgmt.rst27 The user application can monitor these events if it needs to act
/Zephyr-latest/include/zephyr/linker/
Dthread-local-storage.ld16 * These needs to be outside of the tdata/tbss
/Zephyr-latest/cmake/toolchain/xcc/
Dgeneric.cmake20 # lengthens the CMake phase of build, especially when XCC needs to
/Zephyr-latest/samples/sensor/accel_polling/
DREADME.rst15 This sample supports up to 10 3-Axis accelerometers. Each accelerometer needs
/Zephyr-latest/samples/drivers/ipm/ipm_ivshmem/
DREADME.rst10 * QEMU needs to available.
12 ivshmem-server needs to be available and running. The server is available in
16 ivshmem-client needs to be available as it is employed in this sample as an
/Zephyr-latest/doc/services/pm/
Ddevice_runtime.rst13 driver is responsible to indicate when it needs the device and when it does not.
71 indicate when it needs a device and when it does not. The device runtime PM API
73 determine when a device needs to be resumed or suspended. The API uses the *get*
91 indicate it *needs* the device to be active or operational. This function will
121 In a first place, a device driver needs to implement the PM action callback used
148 To enable device runtime power management on a device, the driver needs to call
/Zephyr-latest/boards/shields/rtkmipilcdb00000be/
DKconfig.defconfig24 # so it needs to initialize before the display_ili9806e_dsi driver but after the MIPI DSI driver
/Zephyr-latest/doc/hardware/pinctrl/
Dindex.rst49 more effort, since the driver needs to gather knowledge of peripheral dependent
67 For a device driver to operate correctly, a certain pin configuration needs to
127 achieve that, the device driver needs to have in its scope definitions for the
130 to be supported, a definition named ``PINCTRL_STATE_MYSTATE`` needs to be
171 needs to run onto slightly different boards, each having a peripheral routed at
377 ``pinctrl_soc_pin_t``. This type needs to be defined in a header named
380 needs to define a macro named ``Z_PINCTRL_STATE_PINS_INIT`` that accepts two
382 information the macro needs to define an initializer for all pin configurations
402 ``pinctrl`` API to successfully configure the pins it needs.
404 The device compatible needs to be modified in the corresponding binding so that
[all …]

12345678910>>...21