summaryrefslogtreecommitdiff
path: root/Documentation/serial
diff options
context:
space:
mode:
authorGeert Uytterhoeven <geert+renesas@glider.be>2016-03-14 16:16:10 +0100
committerJonathan Corbet <corbet@lwn.net>2016-03-31 00:58:10 -0600
commit4895b1d72117efea48ff51e94a26ce3cbde4d1a1 (patch)
tree0b97eb3c2e22d281896a1609394986b5cd2f4b81 /Documentation/serial
parent834392a7d92677ff2bdc1c709b1171ee585b55c9 (diff)
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>
Diffstat (limited to 'Documentation/serial')
-rw-r--r--Documentation/serial/driver6
1 files changed, 1 insertions, 5 deletions
diff --git a/Documentation/serial/driver b/Documentation/serial/driver
index e7c6f86ee06f..61d520dea4c6 100644
--- a/Documentation/serial/driver
+++ b/Documentation/serial/driver
@@ -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
are described in the uart_ops listing below.)
-There are three locks. A per-port spinlock, a per-port tmpbuf semaphore,
-and an overall semaphore.
+There are two locks. A per-port spinlock, and an overall semaphore.
From the core driver perspective, the port->lock locks the following
data:
@@ -50,9 +49,6 @@ data:
The low level driver is free to use this lock to provide any additional
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/
removed or reconfigured at inappropriate times. Since v2.6.27, this
semaphore has been the 'mutex' member of the tty_port struct, and