Home
last modified time | relevance | path

Searched refs:buffered (Results 1 – 25 of 39) sorted by relevance

12

/Zephyr-latest/drivers/dac/
Ddac_mcux_dac32.c21 bool buffered; member
57 DAC32_EnableBufferOutput(config->base, config->buffered); in mcux_dac32_channel_setup()
121 .buffered = DT_INST_PROP(n, buffered), \
Ddac_mcux_gau.c48 if (channel_cfg->internal && channel_cfg->buffered) { in nxp_gau_dac_channel_setup()
51 } else if (channel_cfg->buffered) { in nxp_gau_dac_channel_setup()
Ddac_shell.c51 cfg.buffered = true; in cmd_setup()
Ddac_stm32.c111 if (channel_cfg->buffered) { in dac_stm32_channel_setup()
/Zephyr-latest/tests/drivers/i2c/i2c_emul/boards/
Dnative_sim.buf.overlay7 target-buffered-mode;
/Zephyr-latest/subsys/logging/
DKconfig.processing44 int "Number of buffered log messages before flushing"
48 When number of buffered messages reaches the threshold thread is waken
60 number of buffered messages exceeds the threshold (see
70 milliseconds. When started, thread process any buffered messages.
77 milliseconds. When waken up, thread process any buffered messages.
DKconfig.mode15 Log messages are buffered and processed later. This mode has the
Dlog_core.c615 void z_log_dropped(bool buffered) in z_log_dropped() argument
618 if (buffered) { in z_log_dropped()
/Zephyr-latest/subsys/logging/backends/
DKconfig.uart24 In deferred logging mode, sets the maximum number of bytes which can be buffered in
28 In immediate logging mode, processed log messages are not buffered and are always
/Zephyr-latest/include/zephyr/drivers/
Ddac.h48 bool buffered: 1; member
/Zephyr-latest/samples/drivers/dac/src/
Dmain.c31 .buffered = true
/Zephyr-latest/include/zephyr/logging/
Dlog_internal.h39 void z_log_dropped(bool buffered);
/Zephyr-latest/tests/drivers/adc/adc_accuracy_test/src/
Ddac_source.c21 .buffered = true
/Zephyr-latest/drivers/wifi/nrf_wifi/
DKconfig.nrfwifi734 Select the mechanism to retrieve buffered data from AP.
737 bool "PS-Poll frame-based mechanism to retrieve buffered data from AP"
739 When the AP notifies about the availability of buffered data, the STA stays in power save
744 bool "QoS null frame-based mechanism to retrieve buffered data from AP"
746 When the AP notifies about the availability of buffered data, the STA comes out of
747 power save, and then AP can deliver all buffered frames without any additional
749 depending on the delay. It is ideal for heavy buffered traffic.
782 Select the power save exit strategy to retrieve buffered data from AP.
785 bool "Exit power save every time to retrieve buffered data from AP"
787 Exit power save every time to retrieve buffered data from AP. Entering back to
[all …]
/Zephyr-latest/tests/drivers/dac/dac_api/src/
Dtest_dac.c109 .buffered = true
/Zephyr-latest/drivers/can/
DKconfig.loopback43 Number of TX frames that can be buffered.
/Zephyr-latest/doc/services/storage/stream/
Dstream_flash.rst14 There are several reasons why one might want to use buffered writes instead of
/Zephyr-latest/drivers/ethernet/
DKconfig.xmc4xxx20 Number of TX frames which can be buffered in the driver.
/Zephyr-latest/samples/drivers/i2s/echo/
DREADME.rst12 mixes the original signal with its delayed form that is buffered, providing
/Zephyr-latest/tests/bluetooth/tester/
DREADME8 stack. BTP commands and events are received and buffered for further processing
/Zephyr-latest/tests/drivers/dac/dac_loopback/src/
Dtest_dac.c175 .buffered = true
/Zephyr-latest/tests/bluetooth/controller/ctrl_isoal/
DKconfig39 Set the number of Isochronous Rx SDU fragments to be buffered in the
/Zephyr-latest/drivers/sensor/veaa_x_3/
Dveaa_x_3.c161 .buffered = false, in veaa_x_3_init()
/Zephyr-latest/subsys/logging/frontends/
DKconfig57 that any buffered data goes to TPIU/ETR.
/Zephyr-latest/doc/services/tracing/
Dindex.rst533 - buffered:
544 - sync buffered
553 - async buffered
568 - buffered:
577 - sync buffered
585 - async buffered

12