Home
last modified time | relevance | path

Searched refs:progress (Results 1 – 25 of 48) sorted by relevance

12

/Zephyr-latest/doc/services/storage/stream/
Dstream_flash.rst20 Persistent stream write progress
24 the stream write progress to persistent storage so that the operation can resume
28 write progress to persistent storage using the :ref:`Settings <settings_api>`
/Zephyr-latest/subsys/mgmt/hawkbit/
DKconfig200 bool "Save the hawkBit update download progress"
203 Regularly save progress of hawkBit update download operation.
204 When enabled, the download progress is periodically saved to
211 int "Save the hawkBit update download progress interval"
216 Set the interval (in percent) that the hawkBit update download progress will be saved.
217 0 means that the progress will be saved every time a new chunk is downloaded.
/Zephyr-latest/subsys/testsuite/ztest/src/
Dztress.c84 uint32_t progress = 100; in progress_timeout() local
91 progress = (100 * exec_cnt[0]) / tmr_data->exec_cnt; in progress_timeout()
106 progress = MIN(progress, thread_progress); in progress_timeout()
113 printk("\r%u%% remaining:%u ms", progress, (uint32_t)rem); in progress_timeout()
/Zephyr-latest/soc/realtek/ec/
DKconfig11 The RTS5912 BOOTROM needs the information about boot up progress.
/Zephyr-latest/scripts/west_commands/runners/
Dcanopen_program.py15 from progress.bar import Bar
287 progress = Bar('%(percent)d%%', max=size, suffix='%(index)d/%(max)dB')
293 progress.next(n=len(chunk))
297 progress.finish()
/Zephyr-latest/scripts/
Drequirements-base.txt19 progress
/Zephyr-latest/subsys/storage/stream/
DKconfig54 bool "Persistent stream write progress"
58 Enable API for loading and storing the current write progress to flash
/Zephyr-latest/doc/services/resource_management/
Dindex.rst37 state) and cancel (to reclaim client data from an in-progress
50 cancellation has no effect on the in-progress transition.
52 progress: when the service has turned off successfully it will be
/Zephyr-latest/subsys/bluetooth/mesh/
Ddfd_srv.c157 uint8_t progress; in handle_receivers_get() local
176 progress = bt_mesh_dfu_cli_progress(&srv->dfu) / 2; in handle_receivers_get()
186 ((progress & BIT_MASK(6)) << 26U))); in handle_receivers_get()
343 uint8_t progress) in upload_status_rsp_with_progress() argument
360 net_buf_simple_add_u8(&rsp, progress | BIT(7)); in upload_status_rsp_with_progress()
366 net_buf_simple_add_u8(&rsp, progress); in upload_status_rsp_with_progress()
378 uint8_t progress; in upload_status_rsp() local
382 progress = srv->cb->oob_progress_get(srv, srv->upload.slot); in upload_status_rsp()
386 progress = bt_mesh_blob_srv_progress(&srv->upload.blob); in upload_status_rsp()
389 upload_status_rsp_with_progress(srv, ctx, status, progress); in upload_status_rsp()
/Zephyr-latest/tests/arch/arc/arc_dsp_sharing/
DREADME.txt12 tests run concurrently even though they report their progress at different
/Zephyr-latest/boards/beagle/beaglev_fire/doc/
Dindex.rst45 are connected properly you can press the Reset button which will show you a progress bar like:
51 Once you see that progress bar on your screen you can start pressing any button (0-9/a-z) which
130 dd if=<path_to_zephyr.elf> of=/dev/sdXD bs=4M status=progress oflag=sync
/Zephyr-latest/.github/ISSUE_TEMPLATE/
D001_bug_report.md50 What impact does this issue have on your progress (e.g., annoyance, showstopper)
/Zephyr-latest/tests/kernel/fpu_sharing/generic/
DREADME.txt12 tests run concurrently even though they report their progress at different
/Zephyr-latest/subsys/bluetooth/mesh/shell/
Ddfd.c161 uint8_t progress = bt_mesh_dfu_cli_progress(&dfd_srv->dfu) / 2; in cmd_dfd_receivers_get() local
171 t->blob.status, progress, t->img_idx, (i == cnt - 1) ? "" : ","); in cmd_dfd_receivers_get()
Dblob.c149 uint8_t progress = get_progress(info); in xfer_progress() local
154 target->addr, info->phase, progress); in xfer_progress()
Ddfu.c988 SHELL_CMD_ARG(progress, NULL, NULL, cmd_dfu_tx_progress, 1, 0),
998 SHELL_CMD_ARG(progress, NULL, NULL, cmd_dfu_rx_progress, 1, 0),
/Zephyr-latest/subsys/net/l2/ieee802154/
DKconfig115 progress.
/Zephyr-latest/doc/connectivity/networking/api/
Dhttp_server.rst327 the application should be able to keep track of the received data progress.
329 The ``status`` field informs the application about the progress in passing
338 the application shall reset any progress recorded for the resource, and await
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dblob_srv.rst50 The application is notified of the transfer progress through the event handler callbacks, and the
/Zephyr-latest/subsys/usb/device/
DKconfig149 queue from making progress on the USB tasks that would
/Zephyr-latest/doc/project/
Dproposals.rst103 and main stakeholders of the project can make progress on.
Ddev_env_and_tools.rst327 - This PR should not be merged (Do Not Merge). For work in progress, GitHub
398 * - :guilabel:`In progress`
399 - For PRs: is work in progress and should not be merged yet. For issues: Is being
/Zephyr-latest/doc/develop/test/
Dtwister_statuses.rst113 ``STARTED`` (Indicating an in-progress Case).
/Zephyr-latest/tests/bluetooth/tester/src/
Dbtp_mesh.c172 uint8_t progress; member
193 dfd_srv_oob_ctx.progress = 0; in dfd_srv_start_oob_upload()
212 uint8_t progress; in dfd_srv_oob_progress_get() local
215 progress = dfd_srv_oob_ctx.progress; in dfd_srv_oob_progress_get()
217 dfd_srv_oob_ctx.progress = MIN(dfd_srv_oob_ctx.progress + 25, 99); in dfd_srv_oob_progress_get()
219 if (dfd_srv_oob_ctx.progress == 99) { in dfd_srv_oob_progress_get()
223 progress = 0; in dfd_srv_oob_progress_get()
227 progress); in dfd_srv_oob_progress_get()
228 return progress; in dfd_srv_oob_progress_get()
/Zephyr-latest/subsys/bluetooth/audio/
DKconfig.tbs61 an write request if another is already in progress in another thread.

12