serial: doc: Un-document obsolete tmpbuf_sem

uart_info.tmpbuf and uart_info.tmpbuf_sem were removed in v2.6.10, in
full-history-linux commit a797ad7e3ae9cad4 ("[SERIAL] Clean up
serial_core.c write functions.").

Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Geert Uytterhoeven 2016-03-14 16:16:10 +01:00 committed by Jonathan Corbet
parent 834392a7d9
commit 4895b1d721
1 changed files with 1 additions and 5 deletions

View File

@ -36,8 +36,7 @@ It is the responsibility of the low level hardware driver to perform the
necessary locking using port->lock. There are some exceptions (which necessary locking using port->lock. There are some exceptions (which
are described in the uart_ops listing below.) are described in the uart_ops listing below.)
There are three locks. A per-port spinlock, a per-port tmpbuf semaphore, There are two locks. A per-port spinlock, and an overall semaphore.
and an overall semaphore.
From the core driver perspective, the port->lock locks the following From the core driver perspective, the port->lock locks the following
data: data:
@ -50,9 +49,6 @@ data:
The low level driver is free to use this lock to provide any additional The low level driver is free to use this lock to provide any additional
locking. locking.
The core driver uses the info->tmpbuf_sem lock to prevent multi-threaded
access to the info->tmpbuf bouncebuffer used for port writes.
The port_sem semaphore is used to protect against ports being added/ The port_sem semaphore is used to protect against ports being added/
removed or reconfigured at inappropriate times. Since v2.6.27, this removed or reconfigured at inappropriate times. Since v2.6.27, this
semaphore has been the 'mutex' member of the tty_port struct, and semaphore has been the 'mutex' member of the tty_port struct, and