summary refs log tree commit diff
diff options
context:
space:
mode:
authorPeter Korsgaard <jacmet@sunsite.dk>2006-06-02 17:47:26 +0100
committerRussell King <rmk+kernel@arm.linux.org.uk>2006-06-02 17:47:26 +0100
commit89f3da3e06257abba3e70163c92969f3fcd1833d (patch)
treeed67922b84423f0494aa7a6c24093d79a01f2dba
parentba8f5baba79da8eb502f8534c3a8ecb64aceb790 (diff)
downloadlinux-89f3da3e06257abba3e70163c92969f3fcd1833d.tar.gz
[SERIAL] Update parity handling documentation
Update documentation to match reality. INPCK controls whether input
parity checking is enabled.

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
-rw-r--r--Documentation/serial/driver9
1 files changed, 5 insertions, 4 deletions
diff --git a/Documentation/serial/driver b/Documentation/serial/driver
index df82116a9f26..88ad615dd338 100644
--- a/Documentation/serial/driver
+++ b/Documentation/serial/driver
@@ -214,12 +214,13 @@ hardware.
 	The interaction of the iflag bits is as follows (parity error
 	given as an example):
 	Parity error	INPCK	IGNPAR
-	None		n/a	n/a	character received
-	Yes		n/a	0	character discarded
-	Yes		0	1	character received, marked as
+	n/a		0	n/a	character received, marked as
 					TTY_NORMAL
-	Yes		1	1	character received, marked as
+	None		1	n/a	character received, marked as
+					TTY_NORMAL
+	Yes		1	0	character received, marked as
 					TTY_PARITY
+	Yes		1	1	character discarded
 
 	Other flags may be used (eg, xon/xoff characters) if your
 	hardware supports hardware "soft" flow control.