Searched refs:read (Results 201 – 225 of 1064) sorted by relevance
12345678910>>...43
| /Zephyr-latest/drivers/sensor/ist8310/ |
| D | ist8310.h | 42 ist8310_reg_read_fn read; member
|
| /Zephyr-latest/drivers/sdhc/ |
| D | Kconfig.sdhc_cdns | 22 SD host controllers require DMA preparation for read and write operation.
|
| /Zephyr-latest/samples/subsys/modbus/rtu_server/ |
| D | README.rst | 48 for example to control relays or to read ADC values via USB connection without
105 To read LED0, LED1, LED2 state FC05 command (read_coils) can be used.
123 It is also possible to write and read the holding registers.
139 To read holding registers use FC03 command (read_holding_registers).
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_pkt.rst | 15 a means to hold the packet, write and read it, as well as necessary
27 each net_pkt is written and read from the beginning to the end, or
169 following sections: basic read/write access and data access, the
183 within each net_pkt. All read/write operations affect this
184 cursor. Note as well that read or write functions are strict on their
187 exact amount of data that must be read or written.
227 Logically, net_pkt's length is now 15. But if we try to read at this
228 point, it will fail because there is nothing to read at the cursor
230 to read what has been already written by resetting the cursor of the
239 and then let you read the actual 15 bytes present. The cursor is then
[all …]
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 36 read-only area.
41 - A user thread will by default have read/write access to its own stack
51 - A user thread may have read/write access to the stacks of other user
59 - By default, program text and read-only data are accessible to all threads
60 on read-only basis, kernel-wide. This policy may be adjusted.
78 access to read or write, depending on the semantics of the API.
136 typically its stack, program text, read-only data, and any partitions
164 other means, and verify proper read/write access to any memory buffers
|
| /Zephyr-latest/scripts/tracing/ |
| D | trace_capture_uart.py | 48 data = ser.read()
|
| /Zephyr-latest/drivers/gpio/ |
| D | Kconfig.ads114s0x | 17 GPIO controller driver with read/write support.
|
| D | Kconfig.lmp90xxx | 18 GPIO controller driver with read/write support.
|
| /Zephyr-latest/drivers/w1/ |
| D | CMakeLists.txt | 11 # drivers implementing link functions (read, write, reset)
|
| /Zephyr-latest/samples/ |
| D | index.rst | 10 We welcome contributions of new samples to the project and you are encouraged to read more about
|
| /Zephyr-latest/samples/net/cloud/aws_iot_mqtt/src/creds/ |
| D | convert_keys.py | 10 data = f.read()
|
| /Zephyr-latest/drivers/eeprom/ |
| D | eeprom_fake.c | 53 .read = fake_eeprom_read,
|
| D | eeprom_tmp116.c | 57 .read = eeprom_tmp116_read,
|
| /Zephyr-latest/samples/bluetooth/central_hr/ |
| D | README.rst | 5 Connect to a Bluetooth LE heart-rate monitor and read heart-rate measurements.
|
| /Zephyr-latest/samples/bluetooth/central_ht/ |
| D | README.rst | 5 Connect to a Bluetooth LE health thermometer sensor and read temperature measurements.
|
| /Zephyr-latest/subsys/net/lib/mqtt/ |
| D | mqtt_transport.c | 82 return transport_fn[client->transport.type].read(client, data, buflen, in mqtt_transport_read()
|
| /Zephyr-latest/tests/net/lib/lwm2m/interop/pytest/ |
| D | test_portfolio.py | 41 resp = leshan.read(endpoint, '16')
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/settings_mgmt/ |
| D | Kconfig | 55 Maximum length of a value to read, this will be the size of the
66 settings read or write attempt is made.
|
| /Zephyr-latest/subsys/bluetooth/audio/ |
| D | Kconfig.ascs | 57 int "Milliseconds of timeout when handle concurrent access to the long read ASE buffer"
62 an ASE read or dropping a notification if the ASE state is being accessed by another
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | semihost.rst | 22 Semihosting enables files on the host computer to be opened, read, and modified
46 /* Process read data */
|
| /Zephyr-latest/samples/drivers/mspi/mspi_flash/boards/ |
| D | apollo3p_evb.overlay | 45 read-command = <0xEB>;
66 read-command = <0x0B>;
|
| /Zephyr-latest/drivers/counter/ |
| D | counter_nrfx_timer.c | 85 static uint32_t read(const struct device *dev) in read() function
99 *ticks = read(dev); in get_value()
162 now = read(dev); in set_cc()
192 diff = ticks_sub(val - 1, read(dev), top); in set_cc()
270 } else if (read(dev) >= cfg->ticks) { in set_top_value()
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | timers.rst | 10 to read its status.
45 since the status value was last read.
80 A timer's status can be read directly at any time to determine how many times
81 the timer has expired since its status was last read.
83 The amount of time remaining before the timer expires can also be read;
86 A thread may read a timer's status indirectly by **synchronizing**
232 it can read the :ref:`system clock or the hardware clock <kernel_timing>`
|
| /Zephyr-latest/drivers/sensor/st/stm32_digi_temp/ |
| D | Kconfig | 13 is different from the STM32 analog temperature sensor, which is read
|
| /Zephyr-latest/drivers/sensor/bosch/bmp388/ |
| D | bmp388_spi.c | 81 .read = bmp388_reg_read_spi,
|
12345678910>>...43
