/openbmc/linux/Documentation/driver-api/tty/ |
H A D | index.rst | 4 TTY title 7 Teletypewriter (TTY) layer takes care of all those serial devices. Including 10 TTY structures 13 There are several major TTY structures. Every TTY device in a system has a 14 corresponding struct tty_port. These devices are maintained by a TTY driver 19 tty_operations are invoked by the TTY layer. 29 In-detail description of the named TTY structures is in separate documents: 41 Writing TTY Driver 44 Before one starts writing a TTY driver, they must consider 48 directly by the TTY Layer. If you are about to write such a driver, read on. [all …]
|
H A D | tty_port.rst | 4 TTY Port 9 The TTY drivers are advised to use struct tty_port helpers as much as possible. 15 The reference and details are contained in the `TTY Port Reference`_ and `TTY 18 TTY Port Functions 36 TTY Refcounting 42 TTY Helpers 58 TTY Port Reference 66 TTY Port Operations Reference
|
H A D | tty_driver.rst | 4 TTY Driver and TTY Operations 14 allocated structure is filled with information. See `TTY Driver Reference`_ at 19 in `TTY Driver Flags`_ below. 31 TTY Driver Flags 38 :doc: TTY Driver Flags 58 Every TTY device shall be backed by a struct tty_port. Usually, TTY drivers 65 TTY driver is supposed to register every device discovered in the system 71 manage free indices and choosing the right one. The TTY layer only refuses to 74 When the device is opened, the TTY layer allocates struct tty_struct and starts 75 calling operations from :c:member:`tty_driver.ops`, see `TTY Operations [all …]
|
H A D | tty_struct.rst | 4 TTY Struct 9 struct tty_struct is allocated by the TTY layer upon the first open of the TTY 10 device and released after the last close. The TTY layer passes this structure 12 in `TTY Struct Reference`_ at the bottom. 71 TTY Struct Flags 75 :doc: TTY Struct Flags 77 TTY Struct Reference
|
H A D | tty_internals.rst | 4 TTY Internals 12 These functions serve for opening a TTY from the kernelspace:
|
H A D | tty_ldisc.rst | 4 TTY Line Discipline 9 TTY line discipline process all incoming and outgoing character from/to a tty 55 TTY Flags
|
H A D | n_tty.rst | 9 The default (and fallback) :doc:`TTY line discipline <tty_ldisc>`. It tries to
|
/openbmc/linux/drivers/tty/serdev/ |
H A D | Kconfig | 10 Note that you typically also want to enable TTY port controller support. 15 bool "Serial device TTY port controller" 17 Say Y here if you want to use the Serial device bus with common TTY 21 depends on TTY
|
/openbmc/linux/drivers/net/caif/ |
H A D | Kconfig | 15 tristate "CAIF TTY transport driver" 16 depends on CAIF && TTY 19 The CAIF TTY transport driver is a Line Discipline (ldisc) 21 it will redirect the TTY's traffic into the CAIF stack.
|
/openbmc/linux/Documentation/arch/s390/ |
H A D | config3270.sh | 20 TTY=$SUBD/tty 43 echo "grep -v $TTY $INITTAB > $NINITTAB" > $SCRTMP || exit 1 65 echo mknod $D/$TTY$devno c $maj $min >>$SCR 68 echo "echo t$min$GETTYLINE $TTY$devno >> $NINITTAB" >> $SCRTMP
|
/openbmc/linux/net/bluetooth/rfcomm/ |
H A D | Kconfig | 14 bool "RFCOMM TTY support" 16 depends on TTY 18 This option enables TTY emulation support for RFCOMM channels.
|
/openbmc/linux/drivers/tty/ |
H A D | Kconfig | 2 config TTY config 3 bool "Enable TTY" if EXPERT 6 Allows you to remove TTY support which can save space, and 7 blocks features that require TTY from inclusion in the kernel. 8 TTY is required for any text terminals or serial port 11 if TTY 157 characters into a controlling TTY. This continues to be used 175 bool "Automatically load TTY Line Disciplines" 296 tristate "Goldfish TTY Driver" 301 Console and system TTY driver for the Goldfish virtual platform. [all …]
|
/openbmc/linux/Documentation/networking/caif/ |
H A D | caif.rst | 31 There are some things that need to be tweaked to get the host TTY correctly 34 TTY, we are installing our physical serial driver as a line discipline above 35 the TTY device. 38 The benefit is that we can hook up to any TTY. 66 to all CAIF Channels using this TTY.
|
/openbmc/linux/arch/arm/mach-sunplus/ |
H A D | Kconfig | 21 select SERIAL_SUNPLUS if TTY 22 select SERIAL_SUNPLUS_CONSOLE if TTY
|
/openbmc/linux/drivers/s390/char/ |
H A D | Kconfig | 8 depends on CCW && TTY 30 depends on CCW && TTY 48 depends on S390 && TTY 63 depends on S390 && TTY
|
/openbmc/linux/drivers/media/cec/usb/ |
H A D | Kconfig | 5 if USB_SUPPORT && TTY
|
/openbmc/linux/drivers/ipack/devices/ |
H A D | Kconfig | 4 depends on IPACK_BUS && TTY
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | devices.rst | 124 exists, ``/dev/modem`` should point to the appropriate primary TTY device 132 ``/dev/mouse`` may point to a primary serial TTY device, a hardware mouse 161 Terminal, or TTY devices are a special class of character devices. A 244 port TTY, for which no alternate device would exist. 250 other capabilities requiring a TTY line discipline (including SLIP or 257 can be used in the same manner as any TTY device. The master and 259 of a bidirectional pipe with TTY capabilities.
|
/openbmc/obmc-console/ |
H A D | CHANGELOG.md | 57 4. Implement D-Bus interface `xyz.openbmc_project.Console.UART` for UART TTY 63 underlying TTY device is a UART and not a VUART nor PTY (where baud is not
|
/openbmc/u-boot/doc/ |
H A D | README.nokia_rx51 | 80 USB TTY: 82 Maemo kernel 2.6.28 will crash if u-boot enable usb tty. So USB TTY is disabled. 83 For enabling USB TTY just add this line to file include/configs/nokia_rx51.h
|
/openbmc/linux/Documentation/devicetree/bindings/goldfish/ |
H A D | tty.txt | 1 Android Goldfish TTY
|
/openbmc/linux/arch/nios2/ |
H A D | Kconfig.debug | 6 depends on TTY
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/tio/ |
H A D | tio_2.7.bb | 4 connect to serial TTY devices for basic I/O operations."
|
/openbmc/linux/drivers/staging/gdm724x/ |
H A D | Kconfig | 8 depends on NET && USB && TTY && m
|
/openbmc/linux/arch/arm/mach-versatile/ |
H A D | Kconfig | 44 select SERIAL_AMBA_PL010 if TTY 45 select SERIAL_AMBA_PL010_CONSOLE if TTY 122 select SERIAL_AMBA_PL011 if TTY 123 select SERIAL_AMBA_PL011_CONSOLE if TTY
|