brintos

brintos / linux-shallow public Read only

0
0
Text · 5.0 KiB · 895c47f Raw
167 lines · plain
1What:		/sys/class/tty/console/active2Date:		Nov 20103Contact:	Kay Sievers <kay.sievers@vrfy.org>4Description:5		 Shows the list of currently configured6		 console devices, like 'tty1 ttyS0'.7		 The last entry in the file is the active8		 device connected to /dev/console.9		 The file supports poll() to detect virtual10		 console switches.11 12What:		/sys/class/tty/tty<x>/active13Date:		Nov 201014Contact:	Kay Sievers <kay.sievers@vrfy.org>15Description:16		 Shows the currently active virtual console17		 device, like 'tty1'.18		 The file supports poll() to detect virtual19		 console switches.20 21What:		/sys/class/tty/ttyS<x>/uartclk22Date:		Sep 201223Contact:	Tomas Hlavacek <tmshlvck@gmail.com>24Description:25		 Shows the current uartclk value associated with the26		 UART port in serial_core, that is bound to TTY like ttyS0.27		 uartclk = 16 * baud_base28 29		 These sysfs values expose the TIOCGSERIAL interface via30		 sysfs rather than via ioctls.31 32What:		/sys/class/tty/ttyS<x>/type33Date:		October 201234Contact:	Alan Cox <alan@linux.intel.com>35Description:36		 Shows the current tty type for this port.37 38		 These sysfs values expose the TIOCGSERIAL interface via39		 sysfs rather than via ioctls.40 41What:		/sys/class/tty/ttyS<x>/line42Date:		October 201243Contact:	Alan Cox <alan@linux.intel.com>44Description:45		 Shows the current tty line number for this port.46 47		 These sysfs values expose the TIOCGSERIAL interface via48		 sysfs rather than via ioctls.49 50What:		/sys/class/tty/ttyS<x>/port51Date:		October 201252Contact:	Alan Cox <alan@linux.intel.com>53Description:54		 Shows the current tty port I/O address for this port.55 56		 These sysfs values expose the TIOCGSERIAL interface via57		 sysfs rather than via ioctls.58 59What:		/sys/class/tty/ttyS<x>/irq60Date:		October 201261Contact:	Alan Cox <alan@linux.intel.com>62Description:63		 Shows the current primary interrupt for this port.64 65		 These sysfs values expose the TIOCGSERIAL interface via66		 sysfs rather than via ioctls.67 68What:		/sys/class/tty/ttyS<x>/flags69Date:		October 201270Contact:	Alan Cox <alan@linux.intel.com>71Description:72		 Show the tty port status flags for this port.73 74		 These sysfs values expose the TIOCGSERIAL interface via75		 sysfs rather than via ioctls.76 77What:		/sys/class/tty/ttyS<x>/xmit_fifo_size78Date:		October 201279Contact:	Alan Cox <alan@linux.intel.com>80Description:81		 Show the transmit FIFO size for this port.82 83		 These sysfs values expose the TIOCGSERIAL interface via84		 sysfs rather than via ioctls.85 86What:		/sys/class/tty/ttyS<x>/close_delay87Date:		October 201288Contact:	Alan Cox <alan@linux.intel.com>89Description:90		Show the closing delay time for this port in centiseconds.91 92		These sysfs values expose the TIOCGSERIAL interface via93		sysfs rather than via ioctls.94 95What:		/sys/class/tty/ttyS<x>/closing_wait96Date:		October 201297Contact:	Alan Cox <alan@linux.intel.com>98Description:99		Show the close wait time for this port in centiseconds.100 101		Waiting forever is represented as 0. If waiting on close is102		disabled then the value is 65535.103 104		These sysfs values expose the TIOCGSERIAL interface via105		sysfs rather than via ioctls.106 107What:		/sys/class/tty/ttyS<x>/custom_divisor108Date:		October 2012109Contact:	Alan Cox <alan@linux.intel.com>110Description:111		 Show the custom divisor if any that is set on this port.112 113		 These sysfs values expose the TIOCGSERIAL interface via114		 sysfs rather than via ioctls.115 116What:		/sys/class/tty/ttyS<x>/io_type117Date:		October 2012118Contact:	Alan Cox <alan@linux.intel.com>119Description:120		 Show the I/O type that is to be used with the iomem base121		 address.122 123		 These sysfs values expose the TIOCGSERIAL interface via124		 sysfs rather than via ioctls.125 126What:		/sys/class/tty/ttyS<x>/iomem_base127Date:		October 2012128Contact:	Alan Cox <alan@linux.intel.com>129Description:130		 The I/O memory base for this port.131 132		 These sysfs values expose the TIOCGSERIAL interface via133		 sysfs rather than via ioctls.134 135What:		/sys/class/tty/ttyS<x>/iomem_reg_shift136Date:		October 2012137Contact:	Alan Cox <alan@linux.intel.com>138Description:139		 Show the register shift indicating the spacing to be used140		 for accesses on this iomem address.141 142		 These sysfs values expose the TIOCGSERIAL interface via143		 sysfs rather than via ioctls.144 145What:		/sys/class/tty/ttyS<x>/rx_trig_bytes146Date:		May 2014147Contact:	Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>148Description:149		 Shows current RX interrupt trigger bytes or sets the150		 user specified value to change it for the FIFO buffer.151		 Users can show or set this value regardless of opening the152		 serial device file or not.153 154		 The RX trigger can be set one of four kinds of values for UART155		 serials. When users input a meaning less value to this I/F,156		 the RX trigger is changed to the nearest lower value for the157		 device specification. For example, when user sets 7bytes on158		 16550A, which has 1/4/8/14 bytes trigger, the RX trigger is159		 automatically changed to 4 bytes.160 161What:		/sys/class/tty/ttyS<x>/console162Date:		February 2020163Contact:	Andy Shevchenko <andriy.shevchenko@linux.intel.com>164Description:165		 Allows user to detach or attach back the given device as166		 kernel console. It shows and accepts a boolean variable.167