Home
last modified time | relevance | path

Searched refs:busy (Results 101 – 124 of 124) sorted by relevance

12345

/Zephyr-latest/drivers/sdhc/
Dsdhc_cdns_ll.c771 .busy = sdhc_cdns_busy,
/Zephyr-latest/drivers/console/
DKconfig161 If enabled RTT console will busy wait between TX retries when console
/Zephyr-latest/drivers/dma/
Ddma_smartbond.c846 stat->busy = DMA_CTRL_REG_GET_FIELD(DMA_ON, dma_ctrl_reg); in dma_smartbond_get_status()
Ddma_xilinx_axi_dma.c748 stat->busy = !(dma_xilinx_axi_dma_read_reg(&channel_data->channel_regs->dmasr) & in dma_xilinx_axi_dma_get_status()
/Zephyr-latest/drivers/modem/
Dhl7800.c510 bool busy; member
813 static inline void set_busy(bool busy) in set_busy() argument
815 iface_ctx.busy = busy; in set_busy()
927 if (!iface_ctx.busy) { in allow_sleep_work_callback()
942 if (!iface_ctx.restarting && !iface_ctx.busy) { in allow_sleep()
/Zephyr-latest/drivers/usb/udc/
Dudc_smartbond.c1000 ep_cfg->stat.busy = 0; in handle_epx_rx_ev()
1194 data->ep_state[1][i].config.stat.busy = 0; in handle_bus_reset()
/Zephyr-latest/doc/releases/
Drelease-notes-1.7.rst330 * ``ZEP-1487`` - I2C_SS: I2C doesn't set device busy before starting data transfer
331 * ``ZEP-1488`` - SPI_SS: SPI doesn't set device busy before starting data transfer
Drelease-notes-3.7.rst848 * Added support of non busy wait polling in STM32 OSPI driver.
915 being busy more gracefully instead of simply returning errors.
1065 * Removed use of busy wait for single threaded systems.
1528 * Fixed potential busy looping when using :c:func:`zsock_accept` in case of
Drelease-notes-2.2.rst531 * Added PM busy state support in DW driver
823 * :github:`22584` - drivers: spi: spi_mcux_dspi: bus busy status ignored in async
Drelease-notes-4.0.rst1012 * Fixed possible busy-looping in case of errors in the HTTP server sample.
1160 * Fixed possible busy-looping when polling TLS socket for POLLOUT event.
Drelease-notes-2.7.rst714 * Fixed busy looping during DTLS handshake with offloaded sockets.
715 * Fixed busy looping during TLS/DTLS handshake on non blocking sockets.
915 * The APIs to set/clear/check if devices are busy from a power management
Drelease-notes-3.3.rst692 * STM32U5 GPDMA bug fix for busy flag
732 * spi_nor: Added check if the flash is busy during init. This used to cause
2624 - :github:`47120` - shell uart: busy wait for DTR in ISR
3326 * :github:`51713` - drivers: flash: spi_nor: init fails when flash is busy
3336 * :github:`51653` - mgmt: mcumgr: bt: issue with queued packets when device is busy
Drelease-notes-3.5.rst576 * Fixed transfer issue when controller is busy. Now wait for controller to
2196 if there is any device busy.
Drelease-notes-3.2.rst731 * Added support for card busy signal in SDHC SPI driver, to support
1705 - :github:`47120` - shell uart: busy wait for DTR in ISR
2550 * :github:`42574` - i2c: No support for bus recovery imx.rt and or timeout on bus busy
Drelease-notes-3.0.rst1194 * :github:`39942` - usdhc disk_usdhc_access_write busy fail
Drelease-notes-2.6.rst902 * Devices set as busy are no longer suspended by the system power management.
1624 * :github:`33456` - lorawan: unconfirmed messages leave stack in busy state
Drelease-notes-1.14.rst1764 * :github:`12241` - logging: log output busy loops if log output function can not process buffer
1859 * :github:`11502` - Delayed works are not scheduled when system is busy
Drelease-notes-2.4.rst1596 * :github:`25098` - MCUX I2C bus errors leave state machine in busy state
Drelease-notes-2.5.rst1840 * :github:`24652` - sanitycheck doesn't keep my cores busy
Drelease-notes-3.1.rst1188 - :github:`42574` - i2c: No support for bus recovery imx.rt and or timeout on bus busy
/Zephyr-latest/dts/arm/microchip/
Dmec172x_common.dtsi341 * to provide high speed busy wait counter. Keep disabled to
/Zephyr-latest/tests/lib/mpsc_pbuf/src/
Dmain.c1109 .busy = 0, in ZTEST()
/Zephyr-latest/kernel/
DKconfig849 int "Number of CPU loops per microsecond for crude busy looping"
853 Calibration for crude CPU based busy loop duration. The default
/Zephyr-latest/subsys/bluetooth/mesh/
DKconfig181 CONFIG_BT_MESH_RELAY_ADV_SETS are busy with relaying messages
182 and the main advertising set is not busy with sending local
1008 Note: Without a delay between each sent chunk, the network might become too busy with the

12345