driver 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468
  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. Since v2.6.27, this
  42. semaphore has been the 'mutex' member of the tty_port struct, and
  43. commonly referred to as the port mutex (or port->mutex).
  44. uart_ops
  45. --------
  46. The uart_ops structure is the main interface between serial_core and the
  47. hardware specific driver. It contains all the methods to control the
  48. hardware.
  49. tx_empty(port)
  50. This function tests whether the transmitter fifo and shifter
  51. for the port described by 'port' is empty. If it is empty,
  52. this function should return TIOCSER_TEMT, otherwise return 0.
  53. If the port does not support this operation, then it should
  54. return TIOCSER_TEMT.
  55. Locking: none.
  56. Interrupts: caller dependent.
  57. This call must not sleep
  58. set_mctrl(port, mctrl)
  59. This function sets the modem control lines for port described
  60. by 'port' to the state described by mctrl. The relevant bits
  61. of mctrl are:
  62. - TIOCM_RTS RTS signal.
  63. - TIOCM_DTR DTR signal.
  64. - TIOCM_OUT1 OUT1 signal.
  65. - TIOCM_OUT2 OUT2 signal.
  66. - TIOCM_LOOP Set the port into loopback mode.
  67. If the appropriate bit is set, the signal should be driven
  68. active. If the bit is clear, the signal should be driven
  69. inactive.
  70. Locking: port->lock taken.
  71. Interrupts: locally disabled.
  72. This call must not sleep
  73. get_mctrl(port)
  74. Returns the current state of modem control inputs. The state
  75. of the outputs should not be returned, since the core keeps
  76. track of their state. The state information should include:
  77. - TIOCM_CAR state of DCD signal
  78. - TIOCM_CTS state of CTS signal
  79. - TIOCM_DSR state of DSR signal
  80. - TIOCM_RI state of RI signal
  81. The bit is set if the signal is currently driven active. If
  82. the port does not support CTS, DCD or DSR, the driver should
  83. indicate that the signal is permanently active. If RI is
  84. not available, the signal should not be indicated as active.
  85. Locking: port->lock taken.
  86. Interrupts: locally disabled.
  87. This call must not sleep
  88. stop_tx(port)
  89. Stop transmitting characters. This might be due to the CTS
  90. line becoming inactive or the tty layer indicating we want
  91. to stop transmission due to an XOFF character.
  92. The driver should stop transmitting characters as soon as
  93. possible.
  94. Locking: port->lock taken.
  95. Interrupts: locally disabled.
  96. This call must not sleep
  97. start_tx(port)
  98. Start transmitting characters.
  99. Locking: port->lock taken.
  100. Interrupts: locally disabled.
  101. This call must not sleep
  102. send_xchar(port,ch)
  103. Transmit a high priority character, even if the port is stopped.
  104. This is used to implement XON/XOFF flow control and tcflow(). If
  105. the serial driver does not implement this function, the tty core
  106. will append the character to the circular buffer and then call
  107. start_tx() / stop_tx() to flush the data out.
  108. Do not transmit if ch == '\0' (__DISABLED_CHAR).
  109. Locking: none.
  110. Interrupts: caller dependent.
  111. stop_rx(port)
  112. Stop receiving characters; the port is in the process of
  113. being closed.
  114. Locking: port->lock taken.
  115. Interrupts: locally disabled.
  116. This call must not sleep
  117. enable_ms(port)
  118. Enable the modem status interrupts.
  119. This method may be called multiple times. Modem status
  120. interrupts should be disabled when the shutdown method is
  121. called.
  122. Locking: port->lock taken.
  123. Interrupts: locally disabled.
  124. This call must not sleep
  125. break_ctl(port,ctl)
  126. Control the transmission of a break signal. If ctl is
  127. nonzero, the break signal should be transmitted. The signal
  128. should be terminated when another call is made with a zero
  129. ctl.
  130. Locking: none.
  131. Interrupts: caller dependent.
  132. This call must not sleep
  133. startup(port)
  134. Grab any interrupt resources and initialise any low level driver
  135. state. Enable the port for reception. It should not activate
  136. RTS nor DTR; this will be done via a separate call to set_mctrl.
  137. This method will only be called when the port is initially opened.
  138. Locking: port_sem taken.
  139. Interrupts: globally disabled.
  140. shutdown(port)
  141. Disable the port, disable any break condition that may be in
  142. effect, and free any interrupt resources. It should not disable
  143. RTS nor DTR; this will have already been done via a separate
  144. call to set_mctrl.
  145. Drivers must not access port->info once this call has completed.
  146. This method will only be called when there are no more users of
  147. this port.
  148. Locking: port_sem taken.
  149. Interrupts: caller dependent.
  150. flush_buffer(port)
  151. Flush any write buffers, reset any DMA state and stop any
  152. ongoing DMA transfers.
  153. This will be called whenever the port->info->xmit circular
  154. buffer is cleared.
  155. Locking: port->lock taken.
  156. Interrupts: locally disabled.
  157. This call must not sleep
  158. set_termios(port,termios,oldtermios)
  159. Change the port parameters, including word length, parity, stop
  160. bits. Update read_status_mask and ignore_status_mask to indicate
  161. the types of events we are interested in receiving. Relevant
  162. termios->c_cflag bits are:
  163. CSIZE - word size
  164. CSTOPB - 2 stop bits
  165. PARENB - parity enable
  166. PARODD - odd parity (when PARENB is in force)
  167. CREAD - enable reception of characters (if not set,
  168. still receive characters from the port, but
  169. throw them away.
  170. CRTSCTS - if set, enable CTS status change reporting
  171. CLOCAL - if not set, enable modem status change
  172. reporting.
  173. Relevant termios->c_iflag bits are:
  174. INPCK - enable frame and parity error events to be
  175. passed to the TTY layer.
  176. BRKINT
  177. PARMRK - both of these enable break events to be
  178. passed to the TTY layer.
  179. IGNPAR - ignore parity and framing errors
  180. IGNBRK - ignore break errors, If IGNPAR is also
  181. set, ignore overrun errors as well.
  182. The interaction of the iflag bits is as follows (parity error
  183. given as an example):
  184. Parity error INPCK IGNPAR
  185. n/a 0 n/a character received, marked as
  186. TTY_NORMAL
  187. None 1 n/a character received, marked as
  188. TTY_NORMAL
  189. Yes 1 0 character received, marked as
  190. TTY_PARITY
  191. Yes 1 1 character discarded
  192. Other flags may be used (eg, xon/xoff characters) if your
  193. hardware supports hardware "soft" flow control.
  194. Locking: caller holds port->mutex
  195. Interrupts: caller dependent.
  196. This call must not sleep
  197. pm(port,state,oldstate)
  198. Perform any power management related activities on the specified
  199. port. State indicates the new state (defined by
  200. enum uart_pm_state), oldstate indicates the previous state.
  201. This function should not be used to grab any resources.
  202. This will be called when the port is initially opened and finally
  203. closed, except when the port is also the system console. This
  204. will occur even if CONFIG_PM is not set.
  205. Locking: none.
  206. Interrupts: caller dependent.
  207. type(port)
  208. Return a pointer to a string constant describing the specified
  209. port, or return NULL, in which case the string 'unknown' is
  210. substituted.
  211. Locking: none.
  212. Interrupts: caller dependent.
  213. release_port(port)
  214. Release any memory and IO region resources currently in use by
  215. the port.
  216. Locking: none.
  217. Interrupts: caller dependent.
  218. request_port(port)
  219. Request any memory and IO region resources required by the port.
  220. If any fail, no resources should be registered when this function
  221. returns, and it should return -EBUSY on failure.
  222. Locking: none.
  223. Interrupts: caller dependent.
  224. config_port(port,type)
  225. Perform any autoconfiguration steps required for the port. `type`
  226. contains a bit mask of the required configuration. UART_CONFIG_TYPE
  227. indicates that the port requires detection and identification.
  228. port->type should be set to the type found, or PORT_UNKNOWN if
  229. no port was detected.
  230. UART_CONFIG_IRQ indicates autoconfiguration of the interrupt signal,
  231. which should be probed using standard kernel autoprobing techniques.
  232. This is not necessary on platforms where ports have interrupts
  233. internally hard wired (eg, system on a chip implementations).
  234. Locking: none.
  235. Interrupts: caller dependent.
  236. verify_port(port,serinfo)
  237. Verify the new serial port information contained within serinfo is
  238. suitable for this port type.
  239. Locking: none.
  240. Interrupts: caller dependent.
  241. ioctl(port,cmd,arg)
  242. Perform any port specific IOCTLs. IOCTL commands must be defined
  243. using the standard numbering system found in <asm/ioctl.h>
  244. Locking: none.
  245. Interrupts: caller dependent.
  246. poll_init(port)
  247. Called by kgdb to perform the minimal hardware initialization needed
  248. to support poll_put_char() and poll_get_char(). Unlike ->startup()
  249. this should not request interrupts.
  250. Locking: tty_mutex and tty_port->mutex taken.
  251. Interrupts: n/a.
  252. poll_put_char(port,ch)
  253. Called by kgdb to write a single character directly to the serial
  254. port. It can and should block until there is space in the TX FIFO.
  255. Locking: none.
  256. Interrupts: caller dependent.
  257. This call must not sleep
  258. poll_get_char(port)
  259. Called by kgdb to read a single character directly from the serial
  260. port. If data is available, it should be returned; otherwise
  261. the function should return NO_POLL_CHAR immediately.
  262. Locking: none.
  263. Interrupts: caller dependent.
  264. This call must not sleep
  265. Other functions
  266. ---------------
  267. uart_update_timeout(port,cflag,baud)
  268. Update the FIFO drain timeout, port->timeout, according to the
  269. number of bits, parity, stop bits and baud rate.
  270. Locking: caller is expected to take port->lock
  271. Interrupts: n/a
  272. uart_get_baud_rate(port,termios,old,min,max)
  273. Return the numeric baud rate for the specified termios, taking
  274. account of the special 38400 baud "kludge". The B0 baud rate
  275. is mapped to 9600 baud.
  276. If the baud rate is not within min..max, then if old is non-NULL,
  277. the original baud rate will be tried. If that exceeds the
  278. min..max constraint, 9600 baud will be returned. termios will
  279. be updated to the baud rate in use.
  280. Note: min..max must always allow 9600 baud to be selected.
  281. Locking: caller dependent.
  282. Interrupts: n/a
  283. uart_get_divisor(port,baud)
  284. Return the divsor (baud_base / baud) for the specified baud
  285. rate, appropriately rounded.
  286. If 38400 baud and custom divisor is selected, return the
  287. custom divisor instead.
  288. Locking: caller dependent.
  289. Interrupts: n/a
  290. uart_match_port(port1,port2)
  291. This utility function can be used to determine whether two
  292. uart_port structures describe the same port.
  293. Locking: n/a
  294. Interrupts: n/a
  295. uart_write_wakeup(port)
  296. A driver is expected to call this function when the number of
  297. characters in the transmit buffer have dropped below a threshold.
  298. Locking: port->lock should be held.
  299. Interrupts: n/a
  300. uart_register_driver(drv)
  301. Register a uart driver with the core driver. We in turn register
  302. with the tty layer, and initialise the core driver per-port state.
  303. drv->port should be NULL, and the per-port structures should be
  304. registered using uart_add_one_port after this call has succeeded.
  305. Locking: none
  306. Interrupts: enabled
  307. uart_unregister_driver()
  308. Remove all references to a driver from the core driver. The low
  309. level driver must have removed all its ports via the
  310. uart_remove_one_port() if it registered them with uart_add_one_port().
  311. Locking: none
  312. Interrupts: enabled
  313. uart_suspend_port()
  314. uart_resume_port()
  315. uart_add_one_port()
  316. uart_remove_one_port()
  317. Other notes
  318. -----------
  319. It is intended some day to drop the 'unused' entries from uart_port, and
  320. allow low level drivers to register their own individual uart_port's with
  321. the core. This will allow drivers to use uart_port as a pointer to a
  322. structure containing both the uart_port entry with their own extensions,
  323. thus:
  324. struct my_port {
  325. struct uart_port port;
  326. int my_stuff;
  327. };
  328. Modem control lines via GPIO
  329. ----------------------------
  330. Some helpers are provided in order to set/get modem control lines via GPIO.
  331. mctrl_gpio_init(port, idx):
  332. This will get the {cts,rts,...}-gpios from device tree if they are
  333. present and request them, set direction etc, and return an
  334. allocated structure. devm_* functions are used, so there's no need
  335. to call mctrl_gpio_free().
  336. As this sets up the irq handling make sure to not handle changes to the
  337. gpio input lines in your driver, too.
  338. mctrl_gpio_free(dev, gpios):
  339. This will free the requested gpios in mctrl_gpio_init().
  340. As devm_* function are used, there's generally no need to call
  341. this function.
  342. mctrl_gpio_to_gpiod(gpios, gidx)
  343. This returns the gpio structure associated to the modem line index.
  344. mctrl_gpio_set(gpios, mctrl):
  345. This will sets the gpios according to the mctrl state.
  346. mctrl_gpio_get(gpios, mctrl):
  347. This will update mctrl with the gpios values.
  348. mctrl_gpio_enable_ms(gpios):
  349. Enables irqs and handling of changes to the ms lines.
  350. mctrl_gpio_disable_ms(gpios):
  351. Disables irqs and handling of changes to the ms lines.