From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-kernel@vger.kernel.org
Cc: Tilman Schmidt <tilman@imap.cc>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Subject: [PATCH 7/8] docs: serial/tty, add to ldisc methods
Date: Wed, 04 Nov 2009 16:04:52 -0800 [thread overview]
Message-ID: <12573794921501@xenotime.net> (raw)
In-Reply-To: <1257379492822@xenotime.net>
From: Tilman Schmidt <tilman@imap.cc>
Subject: Doc: update serial/tty.txt ldisc methods
A small addition to the ldisc method descriptions.
Impact: Documentation
Signed-off-by: Tilman Schmidt <tilman@imap.cc>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
---
Documentation/serial/tty.txt | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
--- lnx-2632-rc6.orig/Documentation/serial/tty.txt
+++ lnx-2632-rc6/Documentation/serial/tty.txt
@@ -42,7 +42,8 @@ TTY side interfaces:
open() - Called when the line discipline is attached to
the terminal. No other call into the line
discipline for this tty will occur until it
- completes successfully. Can sleep.
+ completes successfully. Returning an error will
+ prevent the ldisc from being attached. Can sleep.
close() - This is called on a terminal when the line
discipline is being unplugged. At the point of
@@ -52,7 +53,7 @@ close() - This is called on a terminal
hangup() - Called when the tty line is hung up.
The line discipline should cease I/O to the tty.
No further calls into the ldisc code will occur.
- Can sleep.
+ The return value is ignored. Can sleep.
write() - A process is writing data through the line
discipline. Multiple write calls are serialized
@@ -83,6 +84,10 @@ ioctl() - Called when an ioctl is hande
that might be for the ldisc. Multiple ioctl calls
may occur in parallel. May sleep.
+compat_ioctl() - Called when a 32 bit ioctl is handed to the tty layer
+ that might be for the ldisc. Multiple ioctl calls
+ may occur in parallel. May sleep.
+
Driver Side Interfaces:
receive_buf() - Hand buffers of bytes from the driver to the ldisc
--
next prev parent reply other threads:[~2009-11-05 0:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 0:04 [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Randy Dunlap
2009-11-05 0:04 ` [PATCH 2/8] docs: " Randy Dunlap
2009-11-05 0:04 ` [PATCH 4/8] docbook: signal_pending has an argument Randy Dunlap
2009-11-05 0:04 ` [PATCH 8/8] docs: use misc-devices/ dir for drivers Randy Dunlap
2009-11-05 0:04 ` [PATCH 3/8] docs: use DMA_BIT_MASK Randy Dunlap
2009-11-05 0:04 ` [PATCH 6/8] docs: explain procs_running better Randy Dunlap
2009-11-05 0:04 ` Randy Dunlap [this message]
2009-11-05 0:16 ` [PATCH 7/8] docs: serial/tty, add to ldisc methods Alan Cox
2009-11-05 8:10 ` [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12573794921501@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tilman@imap.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox