Home
last modified time | relevance | path

Searched refs:retrieved (Results 1 – 25 of 26) sorted by relevance

12

/Zephyr-Core-3.5.0/subsys/stats/
DKconfig9 and usage monitoring. Statistics can be retrieved with the mcumgr
/Zephyr-Core-3.5.0/subsys/usb/device_next/class/
Dusbd_msc_scsi.c903 size_t retrieved = 0; in scsi_read_data() local
908 retrieved = ctx->read_cb(ctx, buf); in scsi_read_data()
910 ctx->remaining_data -= retrieved; in scsi_read_data()
911 if (retrieved == 0) { in scsi_read_data()
915 return retrieved; in scsi_read_data()
/Zephyr-Core-3.5.0/subsys/storage/flash_map/
DKconfig41 If enabled the label property of the flash map can be retrieved
/Zephyr-Core-3.5.0/samples/drivers/led_lp50xx/
DREADME.rst12 First, for each LED information is retrieved using the led_get_info syscall
/Zephyr-Core-3.5.0/samples/subsys/nvs/
DREADME.rst13 the application reboots, and the reboot counter data is retrieved.
/Zephyr-Core-3.5.0/drivers/dai/intel/dmic/
DKconfig.dmic28 All registers configuration is retrieved from blob. The
/Zephyr-Core-3.5.0/doc/kernel/data_structures/
Dslist.rst21 The end nodes of a list may be retrieved with
29 The container struct pointer may be retrieved from a list node using
Dring_buffers.rst134 Data can be retrieved from a ring buffer through copying
142 The amount freed can be less than or equal or to the retrieved amount.
326 /* Requested amount of bytes retrieved. */
330 Data can be retrieved from a **byte mode** ring buffer by direct
/Zephyr-Core-3.5.0/doc/services/mem_mgmt/
Dindex.rst8 region can then be retrieved at run-time by leveraging a provided helper
/Zephyr-Core-3.5.0/doc/services/retention/
Dblinfo.rst9 the information retrieved from the bootloader and storing it in the
/Zephyr-Core-3.5.0/doc/services/binary_descriptors/
Dindex.rst26 But it could also be retrieved by ``west bindesc``:
/Zephyr-Core-3.5.0/kernel/
DKconfig.vm130 retrieved from the backing store. This is much better for system
DKconfig504 together and for that information to be easily retrieved by
/Zephyr-Core-3.5.0/doc/services/settings/
Dindex.rst122 retrieved.
/Zephyr-Core-3.5.0/doc/kernel/services/data_passing/
Dmailboxes.rst196 receiving thread has both received the message and retrieved the message data.
217 has been received and its data retrieved by a receiving thread.
/Zephyr-Core-3.5.0/doc/kernel/services/
Dpolling.rst26 - a kernel FIFO contains data ready to be retrieved
Dinterrupts.rst315 * The argument to the ISR is retrieved and passed to the ISR
/Zephyr-Core-3.5.0/doc/services/tracing/
Dindex.rst186 * RAM (buffer to be retrieved by a debugger)
/Zephyr-Core-3.5.0/tests/cmake/zephyr_get/
DCMakeLists.txt103 # Environment value is cached after it's retrieved.
/Zephyr-Core-3.5.0/scripts/
Dspelling.txt935 retreived||retrieved
/Zephyr-Core-3.5.0/doc/kernel/services/threads/
Dindex.rst536 Thread runtime statistics can be gathered and retrieved if
/Zephyr-Core-3.5.0/doc/services/logging/
Dindex.rst645 identified by source ID and domain ID. Source ID can be retrieved if source name
/Zephyr-Core-3.5.0/subsys/bluetooth/host/
DKconfig368 stack. The remote information is retrieved once a connection has been
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/
Dhci.txt947 by a pair of Handle_Type and Handle is retrieved from the controller.
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-2.5.rst1818 * :github:`25832` - [test][kernel][lpcxpresso55s69_ns] kernel cases meet ESF could not be retrieved

12