Home
last modified time | relevance | path

Searched refs:reads (Results 76 – 94 of 94) sorted by relevance

1234

/Zephyr-latest/boards/phytec/phyboard_polis/doc/
Dindex.rst288 Remoteproc only reads firmware files from the ``/lib/firmware`` directory!
/Zephyr-latest/boards/st/steval_stwinbx1/doc/
Dindex.rst342 (:zephyr:code-sample:`stwinbx1_sensors`) that reads sensors data and outputs
/Zephyr-latest/doc/services/ipc/ipc_service/backends/
Dipc_service_icbmsg.rst188 #. The receiver reads message size and data from his ``rx-region`` starting from the block number r…
/Zephyr-latest/doc/security/
Dsensor-threat.rst178 protect this area from both reads and writes by code that does
/Zephyr-latest/doc/connectivity/networking/api/
Dlwm2m.rst532 internally reads the content of a given resource. This has a side effect that any read callbacks
/Zephyr-latest/doc/connectivity/usb/device/
Dusb_device.rst191 after device is configured. When the host reads the ZLP, which is pretty much
/Zephyr-latest/doc/releases/
Drelease-notes-3.4.rst408 * Added support for long reads and writes for multiple profiles.
410 reads.
Drelease-notes-2.2.rst537 * Optimized reads of MTIME/MTIMECMP on 64-bit RISC-V
731 * :github:`23221` - status register value always reads 0x0000 in eth_mcux_phy_setup
Drelease-notes-1.13.rst454 * :github:`8864` - ARM MPU _arch_buffer_validate allowing reads to kernel memory
Drelease-notes-2.4.rst111 * Established the unrestricted alignment of flash reads for all drivers.
Drelease-notes-2.5.rst1131 * :github:`31385` - ARC version of sys_read32 only reads uint16_t on Zephyr v2.4
Drelease-notes-2.7.rst646 was incorrectly encoded on reads.
Drelease-notes-3.1.rst1318 * :github:`45883` - Bluetooth: Controller: CCM reads data before Radio stores them when DF enabled …
Drelease-notes-2.6.rst1330 * :github:`34669` - uart_read_fifo() reads only 2 chars on nucleo STM32L43KC and nRF52840-DK
Drelease-notes-3.3.rst778 * I2C Added support for dumping messages in the log for all transactions, reads and writes
/Zephyr-latest/doc/kernel/usermode/
Dsyscalls.rst420 However, this is unsafe if the implementation ever does any reads to this
/Zephyr-latest/doc/services/zbus/
Dindex.rst412 if the channel is published twice before the subscriber reads it. The second publication
/Zephyr-latest/doc/hardware/porting/
Darch.rst936 * This reads the value of one hardware register and sends
/Zephyr-latest/doc/
Dzephyr.doxyfile.in2569 # tag file that is based on the input files it reads. See section "Linking to

1234