Home
last modified time | relevance | path

Searched full:terminals (Results 1 – 25 of 32) sorted by relevance

12

/linux-6.12.1/drivers/s390/char/
DKconfig7 prompt "Support for locally attached 3270 terminals"
10 Include support for IBM 3270 terminals.
14 prompt "Support for fullscreen applications on 3270 terminals"
32 Include support for IBM 3215 line-mode terminals.
50 Include support for IBM SCLP line-mode terminals.
/linux-6.12.1/drivers/tty/
DKconfig8 TTY is required for any text terminals or serial port
20 can run several virtual terminals (also called virtual consoles) on
24 an X session, all in parallel. Switching between virtual terminals
31 directly. The fonts used on virtual terminals can be changed with
88 virtual terminals.
106 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
130 terminals. This scheme has a number of problems, including
202 serial ports because they serve many terminals or dial-in
Dtty_jobctrl.c145 * grant write-only access to all terminals for setgid tty in tty_open_proc_set_tty()
/linux-6.12.1/Documentation/devicetree/bindings/pwm/
Dti,twl-pwmled.txt1 Texas Instruments TWL series PWM drivers connected to LED terminals
4 On TWL4030 series: PWMA and PWMB (connected to LEDA and LEDB terminals)
/linux-6.12.1/arch/um/drivers/
DKconfig44 lines to host pseudo-terminals. Access to both traditional
45 pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled
54 lines to host terminals. Access to both virtual consoles
55 (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and
107 traditional pseudo-terminals.
/linux-6.12.1/include/uapi/linux/usb/
Daudio.h149 /* Terminals - 2.1 USB Terminal Types */
196 /* Terminals - 2.2 Input Terminal Types */
205 /* Terminals - control selectors */
223 /* Terminals - 2.3 Output Terminal Types */
233 /* Terminals - 2.4 Bi-directional Terminal Types */
/linux-6.12.1/drivers/comedi/drivers/ni_routing/
DREADME8 when trying to understand how to connect to/from signals and terminals on
47 1) The names of the National Instruments signals/terminals that are used in this
158 abstracted the names of signals/terminals to a common and intuitive set of
/linux-6.12.1/Documentation/devicetree/bindings/power/supply/
Dadc-battery.yaml17 The voltage is expected to be measured between the battery terminals
/linux-6.12.1/Documentation/hwmon/
Dmax31790.rst25 or can be used to modulate the fan's power terminals using an external
/linux-6.12.1/Documentation/devicetree/bindings/input/touchscreen/
Dti,am3359-tsc.yaml41 input lines and terminals respectively are as follows, AIN0 = 0, AIN1 = 1
/linux-6.12.1/include/linux/usb/
Dmidi-v2.h87 __u8 nNumGroupTrm; /* Number of member Group Terminals spanned */
/linux-6.12.1/drivers/media/usb/uvc/
Duvcvideo.h157 * The term 'entity' refers to both UVC units and UVC terminals.
164 * differentiate between units and terminals as long as the descriptor parsing
167 * For terminals, the type's most significant bit stores the terminal
Duvc_driver.c1335 * - one or more Output Terminals (USB Streaming or Display)
1339 * connected to input terminals
1341 * - one or more Input Terminals (Camera, External or USB Streaming)
1470 * output terminals only have an input pin, and thus in uvc_scan_chain_forward()
1513 "Unsupported connection between output terminals %u and %u\n", in uvc_scan_chain_forward()
1700 * Fallback heuristic for devices that don't connect units and terminals in a
1721 * Start by locating the input and output terminals. We only support in uvc_scan_fallback()
1793 * Chains are scanned starting at their output terminals and walked backwards.
1807 * terminals, where all output terminals beside the first one in uvc_scan_device()
/linux-6.12.1/Documentation/userspace-api/media/dvb/
Dintro.rst43 standard Linux Digital TV API. As a commitment to the development of terminals
/linux-6.12.1/include/uapi/linux/
Dcomedi.h952 /* *** BEGIN GLOBALLY-NAMED NI TERMINALS/SIGNALS *** */
967 * when trying to understand how to connect to/from signals and terminals on
987 * by releasing a new API that abstracted the names of signals/terminals to a
1104 /* *** END GLOBALLY-NAMED NI TERMINALS/SIGNALS *** */
/linux-6.12.1/include/linux/
Dsysctl.h111 * mirrored under /proc/sys (non-terminals are handled by a built-in
/linux-6.12.1/drivers/pwm/
Dpwm-twl-led.c36 * This driver handles the PWM driven LED terminals of TWL4030 and TWL6030.
DKconfig710 Generic PWM framework driver for TWL4030/6030 LED terminals.
/linux-6.12.1/arch/um/os-Linux/
Dsigio.c539 printk(UM_KERN_WARNING "No pseudo-terminals available - " in check_sigio()
/linux-6.12.1/tools/perf/util/
Dparse-events.y131 * Entry points. We are either parsing events or terminals. Just terminal
/linux-6.12.1/Documentation/ABI/testing/
Dconfigfs-usb-gadget-uvc135 baSourceID list of the IDs of the units or terminals
/linux-6.12.1/drivers/comedi/drivers/
Dni_routes.c556 MODULE_DESCRIPTION("Comedi helper for routing signals-->terminals for NI");
/linux-6.12.1/tools/bpf/bpftool/Documentation/
Dbpftool-prog.rst344 | Run in separate terminals:
/linux-6.12.1/kernel/debug/kdb/
Dkdb_io.c155 * some terminals send _both_ CR and LF. Avoid having to handle in kdb_getchar()
/linux-6.12.1/Documentation/networking/
Dsnmp_counter.rst1507 On client, run 3 nc commands in different terminals::
1739 On nstat-b, open two terminals, run two nc commands to listen on both

12