| /Zephyr-latest/doc/develop/west/ |
| D | install.rst | 46 .. _west-shell-completion:
48 Enabling shell completion
51 West currently supports shell completion in the following shells:
57 In order to enable shell completion, you will need to obtain the corresponding
58 completion script and have it sourced.
59 Using the completion scripts:
69 source <(west completion bash)
75 … west completion bash > ~/west-completion.bash; echo "source ~/west-completion.bash" >> ~/.bashrc
83 source <(west completion zsh)
89 west completion zsh > "${fpath[1]}/_west"
[all …]
|
| D | zephyr-cmds.rst | 30 .. _west-completion:
32 Shell completion scripts: ``west completion``
35 The ``completion`` extension command outputs shell completion scripts that can
36 then be used directly to enable shell completion for the supported shells.
46 west help completion
|
| /Zephyr-latest/samples/subsys/rtio/sensor_batch_processing/ |
| D | README.rst | 48 D: Consumed completion event 0
49 D: Consumed completion event 1
50 D: Consumed completion event 2
51 D: Consumed completion event 3
74 D: Consumed completion event 0
|
| /Zephyr-latest/subsys/rtio/ |
| D | Kconfig | 15 thread for each completion queue event until the wait count is met. This
17 use polling on the completion queue with a k_yield() in between iterations.
27 calling thread for each completion queue event until the wait count is met.
29 will use polling on the completion queue with a k_yield() in between
|
| /Zephyr-latest/include/zephyr/drivers/console/ |
| D | console.h | 43 uint8_t (*completion)(char *str, uint8_t len));
|
| D | uart_console.h | 31 uint8_t (*completion)(char *str, uint8_t len));
|
| /Zephyr-latest/doc/connectivity/usb/device/api/ |
| D | usb_device.rst | 14 Upon completion the registered endpoint callback will be called. Before
15 sending another packet the class driver should wait for the completion of
|
| /Zephyr-latest/tests/subsys/rtio/rtio_api/src/ |
| D | rtio_iodev_test.h | 33 static void rtio_iodev_test_next(struct rtio_iodev_test_data *data, bool completion) in rtio_iodev_test_next() argument
39 if (!completion && data->txn_head != NULL) { in rtio_iodev_test_next()
|
| /Zephyr-latest/drivers/console/ |
| D | uart_console.c | 568 uint8_t (*completion)(char *str, uint8_t len)) in uart_register_input()
572 completion_cb = completion; in uart_register_input()
579 uint8_t (*completion)(char *str, uint8_t len)) in uart_register_input()
583 ARG_UNUSED(completion); in uart_register_input()
|
| /Zephyr-latest/drivers/i2c/ |
| D | i2c_lpc11u6x.h | 90 struct k_sem completion; member
|
| D | i2c_lpc11u6x.c | 102 k_sem_take(&data->completion, K_FOREVER); in lpc11u6x_i2c_transfer()
302 k_sem_give(&data->completion); in lpc11u6x_i2c_isr()
335 k_sem_init(&data->completion, 0, 1); in lpc11u6x_i2c_init()
|
| D | i2c_rtio.c | 73 static bool i2c_rtio_next(struct i2c_rtio *ctx, bool completion) in i2c_rtio_next() argument
78 if (!completion && ctx->txn_head != NULL) { in i2c_rtio_next()
|
| /Zephyr-latest/soc/native/inf_clock/ |
| D | Kconfig.soc | 8 clock. That means the CPU will always run in zero time until completion after
|
| /Zephyr-latest/drivers/adc/ |
| D | Kconfig.ads114s0x | 40 int "Timeout for wait for completion of a read in ms"
|
| /Zephyr-latest/drivers/ipm/ |
| D | Kconfig.imx | 64 Send FW_READY reply to check for FW boot completion
|
| /Zephyr-latest/drivers/dma/ |
| D | Kconfig.iproc_pax | 45 PAX DMA API blocks until dma completion alert is
|
| /Zephyr-latest/drivers/i3c/ |
| D | i3c_rtio.c | 75 static bool i3c_rtio_next(struct i3c_rtio *ctx, bool completion) in i3c_rtio_next() argument
80 if (!completion && ctx->txn_head != NULL) { in i3c_rtio_next()
|
| /Zephyr-latest/doc/project/ |
| D | modifying_contributions.rst | 31 * drive stale pull requests to completion so they can be merged
48 is done to drive the pull request review to completion, when the pull
|
| /Zephyr-latest/doc/hardware/peripherals/eeprom/ |
| D | shell.rst | 36 also support tab-completion of their arguments.
40 which also supports tab-completion. A list of all devices available can be obtained using the
|
| /Zephyr-latest/drivers/mspi/ |
| D | Kconfig | 38 The tolerance value in ms for the MSPI completion timeout logic.
|
| /Zephyr-latest/drivers/spi/ |
| D | Kconfig.max32 | 45 int "Number of available completion queue entries"
|
| /Zephyr-latest/samples/subsys/profiling/perf/ |
| D | README.rst | 33 * Wait for the completion message ``perf done!``, or ``perf buf override!`` if
|
| /Zephyr-latest/doc/services/ |
| D | notify.rst | 12 available so a busy-wait for completion may be needed.
|
| /Zephyr-latest/doc/services/rtio/ |
| D | index.rst | 47 create concurrent sequential requests. A second queue for completion queue events.
94 In order to know when a sqe has completed there is a completion
95 queue (cq) with completion queue events (cqe). A sqe once completed results in
99 Other potential schemes are possible but a completion queue is a well trod
115 Turning submission queue entries (sqe) into completion queue events (cqe) is the
|
| /Zephyr-latest/doc/services/resource_management/ |
| D | index.rst | 67 Transition operation completion notifications are provided through
74 before issuing completion notifications associated with the new
|
