Home
last modified time | relevance | path

Searched refs:effect (Results 1 – 25 of 105) sorted by relevance

12345

/Zephyr-latest/drivers/sensor/ti/tmag5170/
DKconfig1 # Texas Instruments TMAG5170 high-precision, linear 3D Hall-effect sensor with SPI bus interface
7 bool "TMAG5170 SPI Hall-effect sensor driver"
12 Enable driver for TMAG5170 Hall-effect sensor driver
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Ddfu_cli.h60 uint8_t effect; member
74 enum bt_mesh_dfu_effect effect; member
84 enum bt_mesh_dfu_effect effect; member
Ddfu_srv.h83 enum bt_mesh_dfu_effect *effect);
190 uint8_t effect; member
/Zephyr-latest/samples/drivers/i2s/echo/
DREADME.rst5 Process an audio stream to add an echo effect.
13 a simple echo effect.
47 Press Button 1 to toggle the echo effect and Button 2 to stop the streams.
DKconfig10 bool "Toggle echo effect when pressing sw0"
/Zephyr-latest/subsys/bluetooth/mesh/
Ddfu_srv.c56 enum bt_mesh_dfu_effect *effect) in metadata_check() argument
58 *effect = BT_MESH_DFU_EFFECT_NONE; in metadata_check()
68 if (srv->cb->check(srv, &srv->imgs[idx], buf, effect)) { in metadata_check()
69 *effect = BT_MESH_DFU_EFFECT_NONE; in metadata_check()
200 enum bt_mesh_dfu_effect effect; in handle_metadata_check() local
207 status = metadata_check(srv, idx, buf, &effect); in handle_metadata_check()
211 net_buf_simple_add_u8(&rsp, (status & BIT_MASK(3)) | (effect << 3)); in handle_metadata_check()
236 net_buf_simple_add_u8(&buf, srv->update.effect); in update_status_rsp()
320 (enum bt_mesh_dfu_effect *)&srv->update.effect); in handle_start()
Ddfu_cli.c224 target->effect == BT_MESH_DFU_EFFECT_UNPROV) { in blob_lost_target()
645 if (target->effect == BT_MESH_DFU_EFFECT_UNPROV) { in confirmed()
723 rsp->effect = net_buf_simple_pull_u8(buf) & BIT_MASK(5); in handle_status()
732 rsp->effect = BT_MESH_DFU_EFFECT_NONE; in handle_status()
768 target->effect = net_buf_simple_pull_u8(buf) & BIT_MASK(5); in handle_status()
796 (target->effect == BT_MESH_DFU_EFFECT_UNPROV || in handle_status()
951 rsp->effect = (hdr >> 3); in handle_metadata_status()
/Zephyr-latest/soc/nxp/mcx/
DKconfig8 # effect rather than the family config.
DKconfig.defconfig8 # effect rather than the family config.
/Zephyr-latest/boards/st/nucleo_l552ze_q/
DKconfig.defconfig10 # Not defining LIBC malloc arena has the effect of declaring all available RAM
/Zephyr-latest/boards/st/stm32l562e_dk/
DKconfig.defconfig35 # Not defining LIBC malloc arena has the effect of declaring all available RAM
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Ddfu.rst124 incoming firmware update, and what the effect of the update would be. The metadata format is
195 Firmware effect
199 This may have an effect on the provisioning data of the node and how the Distributor finalizes the
205 The device stays provisioned after the new firmware is programmed. This effect is chosen if the
208 This effect is chosen when the composition data changes and the device doesn't support the remote
211 This effect is chosen when the composition data changes and the device supports the remote
215 This effect is chosen if the composition data in the new firmware changes, the device doesn't
216 support the remote provisioning, and the new composition data takes effect after applying the
221 then process the metadata and provide the effect value. If the effect is
307 response to the Firmware Update Client, indicating if the firmware update will have any effect on
Drpr_srv.rst30 …f a device gets changed after device firmware update (see :ref:`firmware effect <bluetooth_mesh_df…
Ddfu_srv.rst48 :c:enum:`bt_mesh_dfu_effect`. The DFU effect return parameter will be communicated back to the
49 Distributor, and should indicate what effect the firmware update will have on the mesh state of the
58 unprovisioned, this should be communicated through the effect parameter of the metadata check.
/Zephyr-latest/subsys/bluetooth/controller/
DKconfig.df209 will have no effect.
220 no effect.
231 no effect.
243 no effect.
254 no effect.
/Zephyr-latest/doc/develop/api/
Dterminology.rst7 allowed calling context (thread, ISR, pre-kernel), the effect of a call
19 effect whether invoked from interrupt or thread context
22 initialized and will have its specified effect when invoked from that
/Zephyr-latest/tests/bsim/bluetooth/mesh/src/
Dtest_dfu.c173 enum bt_mesh_dfu_effect *effect) in target_metadata_check() argument
175 *effect = dfu_target_effect; in target_metadata_check()
525 if (dfd_srv.targets[i].effect == BT_MESH_DFU_EFFECT_UNPROV) { in dist_dfu_start_and_confirm()
794 static void target_test_effect(enum bt_mesh_dfu_effect effect) in target_test_effect() argument
796 dfu_target_effect = effect; in target_test_effect()
/Zephyr-latest/drivers/flash/
DKconfig.nor59 This is the wait delay (in us) to allow for CS switching to take effect
/Zephyr-latest/doc/develop/west/
Dsign.rst55 above has the same effect as appending them on command line after ``--`` like this:
/Zephyr-latest/doc/kernel/services/synchronization/
Dcondvar.rst61 The following code has the same effect as the code segment above.
Dsemaphores.rst72 The following code has the same effect as the code segment above.
/Zephyr-latest/doc/hardware/peripherals/
Ddma.rst13 peripheral interactions, and features. The API in effect provides a union of all useful DMA
/Zephyr-latest/subsys/bluetooth/mesh/shell/
Ddfu.c79 enum bt_mesh_dfu_effect *effect) in dfu_meta_check() argument
602 shell_print(sh, "\tEffect: %u", rsp.effect); in cmd_dfu_target_state()
707 shell_print(sh, "\tEffect: 0x%x", rsp.effect); in cmd_dfu_target_check()
/Zephyr-latest/tests/kconfig/configdefault/
DKconfig178 # Multiple symbols, no configdefault effect
/Zephyr-latest/doc/releases/
Dindex.rst103 - Treewide changes that have an effect (e.g. changing the include path or

12345