sysfs-tty 4.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156
  1. What: /sys/class/tty/console/active
  2. Date: Nov 2010
  3. Contact: Kay Sievers <kay.sievers@vrfy.org>
  4. Description:
  5. Shows the list of currently configured
  6. console devices, like 'tty1 ttyS0'.
  7. The last entry in the file is the active
  8. device connected to /dev/console.
  9. The file supports poll() to detect virtual
  10. console switches.
  11. What: /sys/class/tty/tty0/active
  12. Date: Nov 2010
  13. Contact: Kay Sievers <kay.sievers@vrfy.org>
  14. Description:
  15. Shows the currently active virtual console
  16. device, like 'tty1'.
  17. The file supports poll() to detect virtual
  18. console switches.
  19. What: /sys/class/tty/ttyS0/uartclk
  20. Date: Sep 2012
  21. Contact: Tomas Hlavacek <tmshlvck@gmail.com>
  22. Description:
  23. Shows the current uartclk value associated with the
  24. UART port in serial_core, that is bound to TTY like ttyS0.
  25. uartclk = 16 * baud_base
  26. These sysfs values expose the TIOCGSERIAL interface via
  27. sysfs rather than via ioctls.
  28. What: /sys/class/tty/ttyS0/type
  29. Date: October 2012
  30. Contact: Alan Cox <alan@linux.intel.com>
  31. Description:
  32. Shows the current tty type for this port.
  33. These sysfs values expose the TIOCGSERIAL interface via
  34. sysfs rather than via ioctls.
  35. What: /sys/class/tty/ttyS0/line
  36. Date: October 2012
  37. Contact: Alan Cox <alan@linux.intel.com>
  38. Description:
  39. Shows the current tty line number for this port.
  40. These sysfs values expose the TIOCGSERIAL interface via
  41. sysfs rather than via ioctls.
  42. What: /sys/class/tty/ttyS0/port
  43. Date: October 2012
  44. Contact: Alan Cox <alan@linux.intel.com>
  45. Description:
  46. Shows the current tty port I/O address for this port.
  47. These sysfs values expose the TIOCGSERIAL interface via
  48. sysfs rather than via ioctls.
  49. What: /sys/class/tty/ttyS0/irq
  50. Date: October 2012
  51. Contact: Alan Cox <alan@linux.intel.com>
  52. Description:
  53. Shows the current primary interrupt for this port.
  54. These sysfs values expose the TIOCGSERIAL interface via
  55. sysfs rather than via ioctls.
  56. What: /sys/class/tty/ttyS0/flags
  57. Date: October 2012
  58. Contact: Alan Cox <alan@linux.intel.com>
  59. Description:
  60. Show the tty port status flags for this port.
  61. These sysfs values expose the TIOCGSERIAL interface via
  62. sysfs rather than via ioctls.
  63. What: /sys/class/tty/ttyS0/xmit_fifo_size
  64. Date: October 2012
  65. Contact: Alan Cox <alan@linux.intel.com>
  66. Description:
  67. Show the transmit FIFO size for this port.
  68. These sysfs values expose the TIOCGSERIAL interface via
  69. sysfs rather than via ioctls.
  70. What: /sys/class/tty/ttyS0/close_delay
  71. Date: October 2012
  72. Contact: Alan Cox <alan@linux.intel.com>
  73. Description:
  74. Show the closing delay time for this port in ms.
  75. These sysfs values expose the TIOCGSERIAL interface via
  76. sysfs rather than via ioctls.
  77. What: /sys/class/tty/ttyS0/closing_wait
  78. Date: October 2012
  79. Contact: Alan Cox <alan@linux.intel.com>
  80. Description:
  81. Show the close wait time for this port in ms.
  82. These sysfs values expose the TIOCGSERIAL interface via
  83. sysfs rather than via ioctls.
  84. What: /sys/class/tty/ttyS0/custom_divisor
  85. Date: October 2012
  86. Contact: Alan Cox <alan@linux.intel.com>
  87. Description:
  88. Show the custom divisor if any that is set on this port.
  89. These sysfs values expose the TIOCGSERIAL interface via
  90. sysfs rather than via ioctls.
  91. What: /sys/class/tty/ttyS0/io_type
  92. Date: October 2012
  93. Contact: Alan Cox <alan@linux.intel.com>
  94. Description:
  95. Show the I/O type that is to be used with the iomem base
  96. address.
  97. These sysfs values expose the TIOCGSERIAL interface via
  98. sysfs rather than via ioctls.
  99. What: /sys/class/tty/ttyS0/iomem_base
  100. Date: October 2012
  101. Contact: Alan Cox <alan@linux.intel.com>
  102. Description:
  103. The I/O memory base for this port.
  104. These sysfs values expose the TIOCGSERIAL interface via
  105. sysfs rather than via ioctls.
  106. What: /sys/class/tty/ttyS0/iomem_reg_shift
  107. Date: October 2012
  108. Contact: Alan Cox <alan@linux.intel.com>
  109. Description:
  110. Show the register shift indicating the spacing to be used
  111. for accesses on this iomem address.
  112. These sysfs values expose the TIOCGSERIAL interface via
  113. sysfs rather than via ioctls.
  114. What: /sys/class/tty/ttyS0/rx_trig_bytes
  115. Date: May 2014
  116. Contact: Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>
  117. Description:
  118. Shows current RX interrupt trigger bytes or sets the
  119. user specified value to change it for the FIFO buffer.
  120. Users can show or set this value regardless of opening the
  121. serial device file or not.
  122. The RX trigger can be set one of four kinds of values for UART
  123. serials. When users input a meaning less value to this I/F,
  124. the RX trigger is changed to the nearest lower value for the
  125. device specification. For example, when user sets 7bytes on
  126. 16550A, which has 1/4/8/14 bytes trigger, the RX trigger is
  127. automatically changed to 4 bytes.