| /Zephyr-latest/drivers/sensor/nxp/p3t1755/ |
| D | p3t1755.h | 37 int (*read)(const struct device *dev, uint8_t reg, uint8_t *byte, uint8_t len); member
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig.sam0 | 24 read/modify/erase/write.
|
| /Zephyr-latest/soc/arm/qemu_virt_arm64/ |
| D | Kconfig.defconfig | 13 # Dummy value, read at runtime
|
| /Zephyr-latest/drivers/modem/ |
| D | modem_context.h | 30 int (*read)(struct modem_iface *iface, uint8_t *buf, size_t size, member
|
| D | modem_iface_uart_interrupt.c | 190 iface->read = modem_iface_uart_read; in modem_iface_uart_init()
203 iface->read = NULL; in modem_iface_uart_init()
|
| D | modem_iface_uart_async.c | 176 iface->read = modem_iface_uart_async_read; in modem_iface_uart_init()
190 iface->read = NULL; in modem_iface_uart_init()
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | peci.rst | 11 The PECI interface allows external devices to read processor temperature,
|
| /Zephyr-latest/boards/waveshare/rp2040_zero/ |
| D | rp2040_zero.dts | 42 read-only;
52 read-only;
|
| /Zephyr-latest/include/zephyr/drivers/ |
| D | i2s.h | 326 int (*read)(const struct device *dev, void **mem_block, size_t *size); member
424 return api->read(dev, mem_block, size); in i2s_read()
|
| /Zephyr-latest/lib/posix/options/ |
| D | device_io.c | 114 ssize_t read(int fd, void *buf, size_t sz) in read() function
119 FUNC_ALIAS(read, _read, ssize_t);
|
| /Zephyr-latest/boards/others/serpente/ |
| D | serpente.dts | 130 read-only;
136 read-only;
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | statistic.rst | 14 An application can read out and clean up statistics at any time.
|
| /Zephyr-latest/subsys/shell/modules/ |
| D | Kconfig | 24 This shell command provides read/write access to physical memory.
|
| /Zephyr-latest/samples/drivers/counter/maxim_ds3231/ |
| D | README.rst | 28 counter value is read, and its value formatted as the date, time, day of
54 Then a synchronization point is read. This takes 894 ms (it must align
60 read sync 0: 1563516002 0 at 2000
62 The alarm configuration is read from non-volatile memory and displayed.
78 We're now 2.131 ms into the run, at which point the alarms are read back
|
| /Zephyr-latest/samples/subsys/modbus/tcp_gateway/ |
| D | README.rst | 74 To read LED0, LED1, LED2 state FC05 command (read_coils) can be used.
92 It is also possible to write and read the holding registers.
108 To read holding registers use FC03 command (read_holding_registers).
|
| /Zephyr-latest/samples/posix/eventfd/src/ |
| D | main.c | 50 s = read(efd, &u, sizeof(uint64_t)); in reader()
|
| /Zephyr-latest/tests/drivers/regulator/voltage/boards/ |
| D | lpcxpresso55s36.overlay | 16 set-read-delay-ms = <10>;
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | memory_domain.rst | 34 - A read-only, executable region or regions for program text and ro-data, that
36 read-only region for ro-data, and a read-only, executable region for text, but
38 threads running in user mode can read ro-data and fetch instructions.
40 - Depending on configuration, user-accessible read-write regions to support
64 which is set to be read-only and is at either the beginning or immediately
152 buffer, plus program text and read-only data. The memory domain APIs are the
162 not allow for the definition of regions which are read-only to user mode but
163 read-write to supervisor mode. A great deal of care must be taken when working
219 a read-write partition for it which may be added to a domain:
247 Automatic memory partitions are only configured as read-write
[all …]
|
| /Zephyr-latest/doc/ |
| D | conf.py | 51 f.read(),
68 sdk_version = f.read().strip()
|
| /Zephyr-latest/boards/adafruit/trinket_m0/ |
| D | adafruit_trinket_m0.dts | 118 read-only;
124 read-only;
|
| /Zephyr-latest/boards/arduino/mkrzero/ |
| D | arduino_mkrzero.dts | 125 read-only;
131 read-only;
|
| /Zephyr-latest/tests/subsys/fs/fat_fs_api/ |
| D | README.txt | 38 Data read:"hello world!"
40 Data read matches data written
|
| /Zephyr-latest/doc/services/rtio/ |
| D | index.rst | 64 register address to then read from. So the sequence of operations might be...
74 can be embodied in a device abstraction that understands a read or write
77 perhaps the read could be done using DMA as its large enough make sense. That
136 In some cases requests to read may not know how much data will be produced.
139 to bind memory to in flight read requests. Instead with memory pools the memory
140 to read into is left to the iodev to allocate from a memory pool associated with
141 the RTIO context that the read was associated with. To create such an RTIO
161 When a read is needed, the caller simply needs to replace the call
165 the mempool. When the read is ready, instead of getting the buffers directly
|
| /Zephyr-latest/drivers/i2s/ |
| D | Kconfig.esp32 | 20 Max number of blocks waiting to be read from the I2S RX channel.
|
| /Zephyr-latest/scripts/logging/dictionary/ |
| D | log_parser_uart.py | 59 data = ser.read(size)
|
