Home
last modified time | relevance | path

Searched refs:progress (Results 1 – 25 of 43) 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/storage/stream/
DKconfig31 bool "Persistent stream write progress"
35 Enable API for loading and storing the current write progress to flash
/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/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
Dspelling.txt1236 progess||progress
1241 progres||progress
1242 progresss||progress
/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.c161 uint8_t progress; in handle_receivers_get() local
180 progress = bt_mesh_dfu_cli_progress(&srv->dfu) / 2; in handle_receivers_get()
190 ((progress & BIT_MASK(6)) << 26U))); in handle_receivers_get()
347 uint8_t progress) in upload_status_rsp_with_progress() argument
364 net_buf_simple_add_u8(&rsp, progress | BIT(7)); in upload_status_rsp_with_progress()
370 net_buf_simple_add_u8(&rsp, progress); in upload_status_rsp_with_progress()
382 uint8_t progress; in upload_status_rsp() local
386 progress = srv->cb->oob_progress_get(srv, srv->upload.slot); in upload_status_rsp()
390 progress = bt_mesh_blob_srv_progress(&srv->upload.blob); in upload_status_rsp()
393 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.c152 uint8_t progress = get_progress(info); in xfer_progress() local
158 target->addr, info->phase, progress); in xfer_progress()
Ddfu.c989 SHELL_CMD_ARG(progress, NULL, NULL, cmd_dfu_tx_progress, 1, 0),
999 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.rst284 the application should be able to keep track of the received data progress.
286 The ``status`` field informs the application about the progress in passing
295 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.rst337 - This PR should not be merged (Do Not Merge). For work in progress, GitHub
408 * - :guilabel:`In progress`
409 - 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/doc/services/device_mgmt/smp_groups/
Dsmp_group_8.rst165 of a file and it is client side responsibility to track progress of upload.
179 of bool flag indicating in-progress upload, last successfully uploaded offset
/Zephyr-latest/subsys/net/ip/
DKconfig.tcp242 "forward progress" event as described in RFC 4861.

12