summaryrefslogtreecommitdiff
path: root/Documentation/serial
diff options
context:
space:
mode:
authorGeert Uytterhoeven <geert+renesas@glider.be>2016-05-11 13:56:04 +0200
committerJonathan Corbet <corbet@lwn.net>2016-05-14 10:18:19 -0600
commit95f981f2e3b9a27ea2eb744b6861a3b9c81a1fde (patch)
treefb6862487573e7fb45b6c8e04c00930898df0771 /Documentation/serial
parent30955e71fc2bd1b966ce6531285ac59ae653819f (diff)
serial: doc: Always refer to tty_port->mutex
Stop referring to the mutex member of the tty_port struct as 'port->mutex', as 'port' is ambiguous, and usually refers to the uart_port struct in this document. Use 'tty_port->mutex' instead, following the single existing use. 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/driver8
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/serial/driver b/Documentation/serial/driver
index 39701515832b..90889c785809 100644
--- a/Documentation/serial/driver
+++ b/Documentation/serial/driver
@@ -57,7 +57,7 @@ locking.
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
-commonly referred to as the port mutex (or port->mutex).
+commonly referred to as the port mutex.
uart_ops
@@ -186,7 +186,7 @@ hardware.
should be terminated when another call is made with a zero
ctl.
- Locking: caller holds port->mutex
+ Locking: caller holds tty_port->mutex
startup(port)
Grab any interrupt resources and initialise any low level driver
@@ -262,14 +262,14 @@ hardware.
Other flags may be used (eg, xon/xoff characters) if your
hardware supports hardware "soft" flow control.
- Locking: caller holds port->mutex
+ Locking: caller holds tty_port->mutex
Interrupts: caller dependent.
This call must not sleep
set_ldisc(port,termios)
Notifier for discipline change. See Documentation/serial/tty.txt.
- Locking: caller holds port->mutex
+ Locking: caller holds tty_port->mutex
pm(port,state,oldstate)
Perform any power management related activities on the specified