Home
last modified time | relevance | path

Searched full:terminal (Results 1 – 25 of 408) sorted by relevance

12345678910>>...17

/Zephyr-latest/dts/bindings/usb/uac2/
Dzephyr,uac2-output-terminal.yaml4 description: USB Audio Class 2 Output Terminal entity
6 compatible: "zephyr,uac2-output-terminal"
9 terminal-type:
13 Terminal Type constant specified in USB Audio Terminal Types
15 assoc-terminal:
18 Associated terminal, e.g. for bidirectional terminal types.
24 Unit or Terminal this terminal receives data from
Dzephyr,uac2-input-terminal.yaml4 description: USB Audio Class 2 Input Terminal entity
6 compatible: "zephyr,uac2-input-terminal"
11 terminal-type:
15 Terminal Type constant specified in USB Audio Terminal Types
17 assoc-terminal:
20 Associated terminal for bi-directional terminal types.
Dzephyr,uac2-clock-source.yaml41 assoc-terminal:
44 Input or Output Terminal associated with this Clock Source. Set if clock
46 Input Terminal) or from input signal on S/PDIF connector.
Dzephyr,uac2-audio-streaming.yaml9 linked-terminal:
13 Input or Output Terminal to which this interface is connected.
63 linked-terminal's clock is sof-synchronized.
/Zephyr-latest/samples/subsys/usb/uac2_implicit_feedback/
Dapp.overlay24 compatible = "zephyr,uac2-input-terminal";
26 terminal-type = <USB_TERMINAL_STREAMING>;
32 compatible = "zephyr,uac2-output-terminal";
35 terminal-type = <BIDIRECTIONAL_TERMINAL_HEADSET>;
36 assoc-terminal = <&mic_input>;
40 compatible = "zephyr,uac2-input-terminal";
42 terminal-type = <BIDIRECTIONAL_TERMINAL_HEADSET>;
44 * provide correct associated terminal ID because the
47 * assoc-terminal = <&headphones_output>;
53 compatible = "zephyr,uac2-output-terminal";
[all …]
/Zephyr-latest/tests/subsys/usb/uac2/
Dapp.overlay25 compatible = "zephyr,uac2-input-terminal";
27 terminal-type = <USB_TERMINAL_STREAMING>;
43 compatible = "zephyr,uac2-output-terminal";
46 terminal-type = <BIDIRECTIONAL_TERMINAL_HEADSET>;
47 assoc-terminal = <&mic_input>;
51 compatible = "zephyr,uac2-input-terminal";
53 terminal-type = <BIDIRECTIONAL_TERMINAL_HEADSET>;
55 * provide correct associated terminal ID because the
58 * assoc-terminal = <&headphones_output>;
73 compatible = "zephyr,uac2-output-terminal";
[all …]
/Zephyr-latest/include/zephyr/usb/class/
Dusbd_uac2.h56 * @brief Terminal update callback
58 * Notifies application that host has enabled or disabled a terminal.
61 * @param terminal Terminal ID linked to AudioStreaming interface
62 * @param enabled True if host enabled terminal, False otherwise
66 void (*terminal_update_cb)(const struct device *dev, uint8_t terminal,
78 * @param terminal Input Terminal ID linked to AudioStreaming interface
82 void *(*get_recv_buf)(const struct device *dev, uint8_t terminal,
91 * @param terminal Input Terminal ID linked to AudioStreaming interface
96 void (*data_recv_cb)(const struct device *dev, uint8_t terminal,
105 * @param terminal Output Terminal ID linked to AudioStreaming interface
[all …]
/Zephyr-latest/scripts/west_commands/runners/
Dminichlink.py22 terminal: bool,
30 self.terminal = terminal
46 "--terminal",
49 help="open the terminal after flashing. Implies --reset.",
61 terminal=args.terminal,
86 if self.reset or self.terminal:
89 if self.terminal:
92 if self.terminal:
/Zephyr-latest/include/zephyr/dt-bindings/usb/
Daudio.h29 /* USB Device Class Definition for Terminal Types
30 * Both "Universal Serial Bus Device Class Definition for Terminal Types"
32 * the same terminal types and values.
35 /* 2.1 USB Terminal Types */
40 /* 2.2 Input Terminal Types */
49 /* 2.3 Output Terminal Types */
59 /* 2.4 Bi-directional Terminal Types */
67 /* 2.5 Telephony Terminal Types */
73 /* 2.6 External Terminal Types */
86 /* 2.7 Embedded Function Terminal Types */
/Zephyr-latest/drivers/serial/
DKconfig.native_posix11 to either connect to the terminal from which the executable was run, or into
21 bool "Connect the UART to its own pseudo terminal"
31 Connect this UART to the stdin & stdout of the calling shell/terminal
35 terminal.
37 shell interactively, as the default terminal configuration is NOT
43 bool "Support waiting for pseudo terminal client readiness"
60 string "Default command to attach the UART to a new terminal"
65 run to attach a new terminal to the 1st UART.
72 'gnome-terminal -- screen %s'
Duart_native_ptty_bottom.c110 * Attempt to connect a terminal emulator to the slave side of the pty
132 * If auto_attach was set, it will also attempt to connect a new terminal
188 * Set terminal in "raw" mode: in np_uart_open_ptty()
197 ERROR("Could not read terminal driver settings\n"); in np_uart_open_ptty()
207 ERROR("Could not change terminal driver settings\n"); in np_uart_open_ptty()
223 ERROR("%s: Could not open terminal from the slave side (%i,%s)\n", in np_uart_open_ptty()
229 ERROR("%s: Could not close terminal from the slave side (%i,%s)\n", in np_uart_open_ptty()
/Zephyr-latest/doc/connectivity/networking/
Dqemu_802154_setup.rst17 For the steps below, you will need two terminal windows:
19 * Terminal #1 is terminal window with ``echo-server`` Zephyr sample application.
20 * Terminal #2 is terminal window with ``echo-client`` Zephyr sample application.
25 Open a terminal window and type:
36 In terminal #1, type:
65 In terminal #2, type:
Dqemu_eth_setup.rst33 For the steps below, you will need two terminal windows:
35 * Terminal #1 is terminal window with net-tools being the current
37 * Terminal #2 is your usual Zephyr development terminal,
58 In terminal #1, type:
78 In terminal #2, type:
Dnetworking_with_multiple_instances.rst29 For the steps below, you will need five terminal windows:
31 * Terminal #1 and #2 are terminal windows with net-tools being the current
33 * Terminal #3, where you setup bridging in Linux host
34 * Terminal #4 and #5 are your usual Zephyr development terminal,
97 In terminal #1, type:
103 In terminal #2, type:
113 In terminal #3, type:
130 In terminal #4, if you are using QEMU, type this:
161 In terminal #5, if you are using QEMU, type this:
Dqemu_setup.rst44 For the steps below, you will need at least 4 terminal windows:
46 * Terminal #1 is your usual Zephyr development terminal, with the Zephyr environment
48 * Terminals #2, #3, and #4 are terminal windows with net-tools being the current
57 In terminal #2, type:
66 In terminal #3, type:
81 In terminal #1, type:
96 Now in terminal #4, you can run various tools to communicate with the
142 To stop the daemons, press Ctrl+C in the corresponding terminal windows
207 samples), you will need two terminal windows, set up for Zephyr development.
209 Terminal #1:
[all …]
Dnative_sim_setup.rst36 For the steps below, you will need three terminal windows:
38 * Terminal #1 is terminal window with net-tools being the current
40 * Terminal #2 is your usual Zephyr development terminal,
42 * Terminal #3 is the console to the running Zephyr native_sim
51 In terminal #1, type:
70 In terminal #2, type:
/Zephyr-latest/samples/subsys/usb/uac2_explicit_feedback/
Dapp.overlay24 compatible = "zephyr,uac2-input-terminal";
26 terminal-type = <USB_TERMINAL_STREAMING>;
32 compatible = "zephyr,uac2-output-terminal";
35 terminal-type = <OUTPUT_TERMINAL_HEADPHONES>;
40 linked-terminal = <&out_terminal>;
/Zephyr-latest/tests/subsys/usb/device_next/
Dbuild_all.overlay26 compatible = "zephyr,uac2-input-terminal";
28 terminal-type = <USB_TERMINAL_STREAMING>;
34 compatible = "zephyr,uac2-output-terminal";
37 terminal-type = <OUTPUT_TERMINAL_HEADPHONES>;
42 linked-terminal = <&out_terminal>;
/Zephyr-latest/doc/develop/getting_started/
Dinstallation_mac.rst12 Terminal application (or any other terminal emulator) are subject to the same
15 macOS will not let you execute those from the Terminal by default. In order to
24 make changes and check the checkbox corresponding to your terminal emulator of
25 choice. This will apply to any executable being launched from such terminal
/Zephyr-latest/samples/subsys/usb/uac2_explicit_feedback/src/
Dmain.c36 * when USB host decides to perform rapid terminal enable/disable cycles.
54 static void uac2_terminal_update_cb(const struct device *dev, uint8_t terminal, in uac2_terminal_update_cb() argument
60 /* This sample has only one terminal therefore the callback can simply in uac2_terminal_update_cb()
61 * ignore the terminal variable. in uac2_terminal_update_cb()
63 __ASSERT_NO_MSG(terminal == HEADPHONES_OUT_TERMINAL_ID); in uac2_terminal_update_cb()
76 static void *uac2_get_recv_buf(const struct device *dev, uint8_t terminal, in uac2_get_recv_buf() argument
84 if (terminal == HEADPHONES_OUT_TERMINAL_ID) { in uac2_get_recv_buf()
88 LOG_ERR("Buffer request on disabled terminal"); in uac2_get_recv_buf()
101 static void uac2_data_recv_cb(const struct device *dev, uint8_t terminal, in uac2_data_recv_cb() argument
115 * either disable terminal (or the cable will be disconnected) in uac2_data_recv_cb()
[all …]
/Zephyr-latest/boards/seeed/wio_terminal/doc/
Dindex.rst6 The Wio Terminal is a small (72 mm x 57 mm x 12 mm) and powerful ARM board with
97 The `Wio Terminal Getting started guide`_ has detailed information about the
123 The Wio Terminal ships with an UF2 bootloader that is BOSSA compatible. The
153 (counting from the top left) user button at the top of the Wio Terminal.
158 In addition to the built-in bootloader, the Wio Terminal can be flashed and
167 Wio Terminal to the :code:`SWCLK`, :code:`SWDIO`, :code:`RESET`,
192 .. _Wio Terminal Getting started guide:
193 https://wiki.seeedstudio.com/Wio-Terminal-Getting-Started/
196 https://wiki.seeedstudio.com/Wio-Terminal-Getting-Started/#pinout-diagram
199 https://wiki.seeedstudio.com/Wio-Terminal-Getting-Started/#resources
[all …]
/Zephyr-latest/doc/develop/
Denv_vars.rst16 lifetime of your current terminal window:
34 This is best for experimentation. If you close your terminal window, use
35 another terminal window or tab, restart your computer, etc., this setting
50 don't affect shell instances already started; try opening a new terminal
58 To use ``setx``, type this command, then close the terminal window. Any
72 You can then run ``rapidee`` from your terminal to launch the program and set
76 you make in RapidEE will be available whenever you open a new terminal window.
98 To get this value back into your current terminal environment, **you must
111 To get this value back into your current terminal environment, **you must
136 into your current terminal's environment. To do so, run this command from the
/Zephyr-latest/samples/drivers/ipm/ipm_ivshmem/
DREADME.rst61 On another terminal window do:
69 on the other terminal window do the same, that is it ``-d path/to/instance_2``
79 terminal window, using the run target:
92 go to the other terminal window and check with ``ivshmem`` command:
122 Then go back to the other terminal window where user may see the reception
123 of the notification on the terminal:
/Zephyr-latest/modules/segger/
DKconfig37 int "Size of the buffer for terminal output of target, up to host"
41 int "Size of the buffer for terminal input of target, from host"
49 prompt "Mode for pre-initialized terminal channel (buffer 0)"
/Zephyr-latest/samples/net/dns_resolve/
DREADME.rst25 - screen terminal emulator or equivalent.
65 Open a terminal window and type:
94 Open a terminal window and type:
137 Open a terminal window and type:
148 Open a terminal window and type:

12345678910>>...17