Home
last modified time | relevance | path

Searched full:overrun (Results 1 – 25 of 107) sorted by relevance

12345

/Zephyr-latest/tests/subsys/fs/littlefs/src/
Dtest_util.c53 char overrun[TESTFS_PATH_MAX + 2] = "/"; in ZTEST() local
54 size_t overrun_max = sizeof(overrun) - 1; in ZTEST()
57 .mnt_point = overrun, in ZTEST()
63 memset(overrun + 1, 'A', overrun_max - 1); in ZTEST()
67 "bad overrun init return"); in ZTEST()
68 zassert_true(strcmp(path.path, overrun) < 0, in ZTEST()
69 "bad overrun init"); in ZTEST()
70 zassert_equal(strncmp(path.path, overrun, path_max), in ZTEST()
72 "bad overrun path"); in ZTEST()
74 "missing overrun EOS"); in ZTEST()
[all …]
/Zephyr-latest/samples/sensor/lis2dh/src/
Dmain.c17 const char *overrun = ""; in fetch_and_display() local
22 /* Sample overrun. Ignore in polled mode. */ in fetch_and_display()
24 overrun = "[OVERRUN] "; in fetch_and_display()
37 count, k_uptime_get_32(), overrun, in fetch_and_display()
/Zephyr-latest/dts/bindings/spi/
Dspi-controller.yaml60 overrun-character:
63 The overrun character (ORC) is used when all bytes from the TX buffer
Dnordic,nrf-spi-common.yaml28 overrun-character:
/Zephyr-latest/dts/bindings/usb/uac2/
Dzephyr,uac2-audio-streaming.yaml46 data-overrun-control:
48 description: Data Overrun capabilities
/Zephyr-latest/tests/drivers/spi/spi_loopback/boards/
Dnrf51dk_nrf51822.overlay8 overrun-character = <0x00>;
Dnrf52dk_nrf52832.overlay8 overrun-character = <0x00>;
Dnrf9160dk_nrf9160.overlay8 overrun-character = <0x00>;
Dnrf52840dk_nrf52840.overlay8 overrun-character = <0x00>;
Dnrf54l15dk_nrf54l15_cpuapp.overlay31 overrun-character = <0x00>;
Dnrf54h20dk_nrf54h20_common.dtsi30 overrun-character = <0x00>;
Dnrf54h20dk_nrf54h20_cpuapp_fast.overlay35 overrun-character = <0x00>;
/Zephyr-latest/tests/drivers/i2s/i2s_api/src/
Dtest_i2s_dir_both_loopback.c180 /** @brief RX buffer overrun.
182 * - In case of RX buffer overrun it is possible to read out RX data blocks
184 * - Reading from an empty RX queue when the RX buffer overrun occurred results
186 * - Sending PREPARE trigger after the RX buffer overrun occurred changes
233 zassert_equal(ret, -EIO, "RX overrun error not detected"); in ZTEST_USER()
Dtest_i2s_loopback.c285 /** @brief RX buffer overrun.
287 * - In case of RX buffer overrun it is possible to read out RX data blocks
289 * - Reading from an empty RX queue when the RX buffer overrun occurred results
291 * - Sending PREPARE trigger after the RX buffer overrun occurred changes
343 zassert_equal(ret, -EIO, "RX overrun error not detected"); in ZTEST_USER()
/Zephyr-latest/drivers/ethernet/
Deth_e1000_priv.h21 #define ICR_RXO (1 << 6) /* Receiver Overrun */
23 #define IMS_RXO (1 << 6) /* Receiver FIFO Overrun */
/Zephyr-latest/subsys/mgmt/ec_host_cmd/backends/
Dec_host_cmd_backend_uart.c65 * host is sending extra bytes which indicates data overrun.
131 LOG_ERR("Request overrun detected"); in rx_timeout()
192 /* Don't wait for overrun, because it is already done in uart_callback()
210 /* Overrun error, set the state and wait for timeout */ in uart_callback()
/Zephyr-latest/drivers/disk/
DKconfig.sdmmc57 overrun (RX mode) errors.
/Zephyr-latest/soc/microchip/mec/common/reg/
Dmec_uart.h39 #define MCHP_UART_IER_ELSI 0x04u /* Errors: Overrun, Parity, Framing, and Break */
66 * Highest priority: Line status, overrun, framing, or break
/Zephyr-latest/tests/drivers/spi/spi_controller_peripheral/boards/
Dnrf52840dk_nrf52840.overlay51 overrun-character = <0x00>;
Dnrf54l15dk_nrf54l15_cpuapp.overlay55 overrun-character = <0x00>;
Dnrf54h20dk_nrf54h20_common.dtsi61 overrun-character = <0x00>;
/Zephyr-latest/tests/drivers/spi/spi_error_cases/boards/
Dnrf52840dk_nrf52840.overlay51 overrun-character = <0x00>;
Dnrf54h20dk_nrf54h20_common.dtsi60 overrun-character = <0x00>;
Dnrf54l15dk_nrf54l15_cpuapp.overlay55 overrun-character = <0x00>;
/Zephyr-latest/drivers/serial/
Duart_pl011_registers.h69 #define PL011_RSR_ECR_OE BIT(3) /* overrun error */
135 #define PL011_IMSC_OEIM BIT(10) /* overrun error interrupt mask */

12345