driver 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398
  1. Low Level Serial API
  2. --------------------
  3. This document is meant as a brief overview of some aspects of the new serial
  4. driver. It is not complete, any questions you have should be directed to
  5. <rmk@arm.linux.org.uk>
  6. The reference implementation is contained within amba_pl011.c.
  7. Low Level Serial Hardware Driver
  8. --------------------------------
  9. The low level serial hardware driver is responsible for supplying port
  10. information (defined by uart_port) and a set of control methods (defined
  11. by uart_ops) to the core serial driver. The low level driver is also
  12. responsible for handling interrupts for the port, and providing any
  13. console support.
  14. Console Support
  15. ---------------
  16. The serial core provides a few helper functions. This includes identifing
  17. the correct port structure (via uart_get_console) and decoding command line
  18. arguments (uart_parse_options).
  19. There is also a helper function (uart_write_console) which performs a
  20. character by character write, translating newlines to CRLF sequences.
  21. Driver writers are recommended to use this function rather than implementing
  22. their own version.
  23. Locking
  24. -------
  25. It is the responsibility of the low level hardware driver to perform the
  26. necessary locking using port->lock. There are some exceptions (which
  27. are described in the uart_ops listing below.)
  28. There are three locks. A per-port spinlock, a per-port tmpbuf semaphore,
  29. and an overall semaphore.
  30. From the core driver perspective, the port->lock locks the following
  31. data:
  32. port->mctrl
  33. port->icount
  34. info->xmit.head (circ->head)
  35. info->xmit.tail (circ->tail)
  36. The low level driver is free to use this lock to provide any additional
  37. locking.
  38. The core driver uses the info->tmpbuf_sem lock to prevent multi-threaded
  39. access to the info->tmpbuf bouncebuffer used for port writes.
  40. The port_sem semaphore is used to protect against ports being added/
  41. removed or reconfigured at inappropriate times.
  42. uart_ops
  43. --------
  44. The uart_ops structure is the main interface between serial_core and the
  45. hardware specific driver. It contains all the methods to control the
  46. hardware.
  47. tx_empty(port)
  48. This function tests whether the transmitter fifo and shifter
  49. for the port described by 'port' is empty. If it is empty,
  50. this function should return TIOCSER_TEMT, otherwise return 0.
  51. If the port does not support this operation, then it should
  52. return TIOCSER_TEMT.
  53. Locking: none.
  54. Interrupts: caller dependent.
  55. This call must not sleep
  56. set_mctrl(port, mctrl)
  57. This function sets the modem control lines for port described
  58. by 'port' to the state described by mctrl. The relevant bits
  59. of mctrl are:
  60. - TIOCM_RTS RTS signal.
  61. - TIOCM_DTR DTR signal.
  62. - TIOCM_OUT1 OUT1 signal.
  63. - TIOCM_OUT2 OUT2 signal.
  64. - TIOCM_LOOP Set the port into loopback mode.
  65. If the appropriate bit is set, the signal should be driven
  66. active. If the bit is clear, the signal should be driven
  67. inactive.
  68. Locking: port->lock taken.
  69. Interrupts: locally disabled.
  70. This call must not sleep
  71. get_mctrl(port)
  72. Returns the current state of modem control inputs. The state
  73. of the outputs should not be returned, since the core keeps
  74. track of their state. The state information should include:
  75. - TIOCM_CAR state of DCD signal
  76. - TIOCM_CTS state of CTS signal
  77. - TIOCM_DSR state of DSR signal
  78. - TIOCM_RI state of RI signal
  79. The bit is set if the signal is currently driven active. If
  80. the port does not support CTS, DCD or DSR, the driver should
  81. indicate that the signal is permanently active. If RI is
  82. not available, the signal should not be indicated as active.
  83. Locking: port->lock taken.
  84. Interrupts: locally disabled.
  85. This call must not sleep
  86. stop_tx(port)
  87. Stop transmitting characters. This might be due to the CTS
  88. line becoming inactive or the tty layer indicating we want
  89. to stop transmission due to an XOFF character.
  90. The driver should stop transmitting characters as soon as
  91. possible.
  92. Locking: port->lock taken.
  93. Interrupts: locally disabled.
  94. This call must not sleep
  95. start_tx(port)
  96. Start transmitting characters.
  97. Locking: port->lock taken.
  98. Interrupts: locally disabled.
  99. This call must not sleep
  100. stop_rx(port)
  101. Stop receiving characters; the port is in the process of
  102. being closed.
  103. Locking: port->lock taken.
  104. Interrupts: locally disabled.
  105. This call must not sleep
  106. enable_ms(port)
  107. Enable the modem status interrupts.
  108. This method may be called multiple times. Modem status
  109. interrupts should be disabled when the shutdown method is
  110. called.
  111. Locking: port->lock taken.
  112. Interrupts: locally disabled.
  113. This call must not sleep
  114. break_ctl(port,ctl)
  115. Control the transmission of a break signal. If ctl is
  116. nonzero, the break signal should be transmitted. The signal
  117. should be terminated when another call is made with a zero
  118. ctl.
  119. Locking: none.
  120. Interrupts: caller dependent.
  121. This call must not sleep
  122. startup(port)
  123. Grab any interrupt resources and initialise any low level driver
  124. state. Enable the port for reception. It should not activate
  125. RTS nor DTR; this will be done via a separate call to set_mctrl.
  126. This method will only be called when the port is initially opened.
  127. Locking: port_sem taken.
  128. Interrupts: globally disabled.
  129. shutdown(port)
  130. Disable the port, disable any break condition that may be in
  131. effect, and free any interrupt resources. It should not disable
  132. RTS nor DTR; this will have already been done via a separate
  133. call to set_mctrl.
  134. Drivers must not access port->info once this call has completed.
  135. This method will only be called when there are no more users of
  136. this port.
  137. Locking: port_sem taken.
  138. Interrupts: caller dependent.
  139. flush_buffer(port)
  140. Flush any write buffers, reset any DMA state and stop any
  141. ongoing DMA transfers.
  142. This will be called whenever the port->info->xmit circular
  143. buffer is cleared.
  144. Locking: port->lock taken.
  145. Interrupts: locally disabled.
  146. This call must not sleep
  147. set_termios(port,termios,oldtermios)
  148. Change the port parameters, including word length, parity, stop
  149. bits. Update read_status_mask and ignore_status_mask to indicate
  150. the types of events we are interested in receiving. Relevant
  151. termios->c_cflag bits are:
  152. CSIZE - word size
  153. CSTOPB - 2 stop bits
  154. PARENB - parity enable
  155. PARODD - odd parity (when PARENB is in force)
  156. CREAD - enable reception of characters (if not set,
  157. still receive characters from the port, but
  158. throw them away.
  159. CRTSCTS - if set, enable CTS status change reporting
  160. CLOCAL - if not set, enable modem status change
  161. reporting.
  162. Relevant termios->c_iflag bits are:
  163. INPCK - enable frame and parity error events to be
  164. passed to the TTY layer.
  165. BRKINT
  166. PARMRK - both of these enable break events to be
  167. passed to the TTY layer.
  168. IGNPAR - ignore parity and framing errors
  169. IGNBRK - ignore break errors, If IGNPAR is also
  170. set, ignore overrun errors as well.
  171. The interaction of the iflag bits is as follows (parity error
  172. given as an example):
  173. Parity error INPCK IGNPAR
  174. n/a 0 n/a character received, marked as
  175. TTY_NORMAL
  176. None 1 n/a character received, marked as
  177. TTY_NORMAL
  178. Yes 1 0 character received, marked as
  179. TTY_PARITY
  180. Yes 1 1 character discarded
  181. Other flags may be used (eg, xon/xoff characters) if your
  182. hardware supports hardware "soft" flow control.
  183. Locking: none.
  184. Interrupts: caller dependent.
  185. This call must not sleep
  186. pm(port,state,oldstate)
  187. Perform any power management related activities on the specified
  188. port. State indicates the new state (defined by ACPI D0-D3),
  189. oldstate indicates the previous state. Essentially, D0 means
  190. fully on, D3 means powered down.
  191. This function should not be used to grab any resources.
  192. This will be called when the port is initially opened and finally
  193. closed, except when the port is also the system console. This
  194. will occur even if CONFIG_PM is not set.
  195. Locking: none.
  196. Interrupts: caller dependent.
  197. type(port)
  198. Return a pointer to a string constant describing the specified
  199. port, or return NULL, in which case the string 'unknown' is
  200. substituted.
  201. Locking: none.
  202. Interrupts: caller dependent.
  203. release_port(port)
  204. Release any memory and IO region resources currently in use by
  205. the port.
  206. Locking: none.
  207. Interrupts: caller dependent.
  208. request_port(port)
  209. Request any memory and IO region resources required by the port.
  210. If any fail, no resources should be registered when this function
  211. returns, and it should return -EBUSY on failure.
  212. Locking: none.
  213. Interrupts: caller dependent.
  214. config_port(port,type)
  215. Perform any autoconfiguration steps required for the port. `type`
  216. contains a bit mask of the required configuration. UART_CONFIG_TYPE
  217. indicates that the port requires detection and identification.
  218. port->type should be set to the type found, or PORT_UNKNOWN if
  219. no port was detected.
  220. UART_CONFIG_IRQ indicates autoconfiguration of the interrupt signal,
  221. which should be probed using standard kernel autoprobing techniques.
  222. This is not necessary on platforms where ports have interrupts
  223. internally hard wired (eg, system on a chip implementations).
  224. Locking: none.
  225. Interrupts: caller dependent.
  226. verify_port(port,serinfo)
  227. Verify the new serial port information contained within serinfo is
  228. suitable for this port type.
  229. Locking: none.
  230. Interrupts: caller dependent.
  231. ioctl(port,cmd,arg)
  232. Perform any port specific IOCTLs. IOCTL commands must be defined
  233. using the standard numbering system found in <asm/ioctl.h>
  234. Locking: none.
  235. Interrupts: caller dependent.
  236. Other functions
  237. ---------------
  238. uart_update_timeout(port,cflag,baud)
  239. Update the FIFO drain timeout, port->timeout, according to the
  240. number of bits, parity, stop bits and baud rate.
  241. Locking: caller is expected to take port->lock
  242. Interrupts: n/a
  243. uart_get_baud_rate(port,termios,old,min,max)
  244. Return the numeric baud rate for the specified termios, taking
  245. account of the special 38400 baud "kludge". The B0 baud rate
  246. is mapped to 9600 baud.
  247. If the baud rate is not within min..max, then if old is non-NULL,
  248. the original baud rate will be tried. If that exceeds the
  249. min..max constraint, 9600 baud will be returned. termios will
  250. be updated to the baud rate in use.
  251. Note: min..max must always allow 9600 baud to be selected.
  252. Locking: caller dependent.
  253. Interrupts: n/a
  254. uart_get_divisor(port,baud)
  255. Return the divsor (baud_base / baud) for the specified baud
  256. rate, appropriately rounded.
  257. If 38400 baud and custom divisor is selected, return the
  258. custom divisor instead.
  259. Locking: caller dependent.
  260. Interrupts: n/a
  261. uart_match_port(port1,port2)
  262. This utility function can be used to determine whether two
  263. uart_port structures describe the same port.
  264. Locking: n/a
  265. Interrupts: n/a
  266. uart_write_wakeup(port)
  267. A driver is expected to call this function when the number of
  268. characters in the transmit buffer have dropped below a threshold.
  269. Locking: port->lock should be held.
  270. Interrupts: n/a
  271. uart_register_driver(drv)
  272. Register a uart driver with the core driver. We in turn register
  273. with the tty layer, and initialise the core driver per-port state.
  274. drv->port should be NULL, and the per-port structures should be
  275. registered using uart_add_one_port after this call has succeeded.
  276. Locking: none
  277. Interrupts: enabled
  278. uart_unregister_driver()
  279. Remove all references to a driver from the core driver. The low
  280. level driver must have removed all its ports via the
  281. uart_remove_one_port() if it registered them with uart_add_one_port().
  282. Locking: none
  283. Interrupts: enabled
  284. uart_suspend_port()
  285. uart_resume_port()
  286. uart_add_one_port()
  287. uart_remove_one_port()
  288. Other notes
  289. -----------
  290. It is intended some day to drop the 'unused' entries from uart_port, and
  291. allow low level drivers to register their own individual uart_port's with
  292. the core. This will allow drivers to use uart_port as a pointer to a
  293. structure containing both the uart_port entry with their own extensions,
  294. thus:
  295. struct my_port {
  296. struct uart_port port;
  297. int my_stuff;
  298. };