linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: linux-serial@vger.kernel.org
Subject: Re: better Documentation for TIOCM_CTS handling
Date: Thu, 25 Sep 2008 15:14:50 +0200	[thread overview]
Message-ID: <48DB8ECA.1020302@parrot.com> (raw)
In-Reply-To: <48D242DC.30102@parrot.com>

[-- Attachment #1: Type: text/plain, Size: 216 bytes --]

Hi,

can we add in the documentation that if the driver want to manage CTS or
DCD, it should be able to report the change with uart_handle_xx_change
function ?

Something like the attached patch.


Thanks


Matthieu

[-- Attachment #2: uart_doc --]
[-- Type: text/plain, Size: 663 bytes --]

diff --git a/Documentation/serial/driver b/Documentation/serial/driver
index 77ba0af..8395d5a 100644
--- a/Documentation/serial/driver
+++ b/Documentation/serial/driver
@@ -109,6 +109,10 @@ hardware.
 	the port does not support CTS, DCD or DSR, the driver should
 	indicate that the signal is permanently active.  If RI is
 	not available, the signal should not be indicated as active.
+	If the port does not support automatic detection of change of
+	CTS or DCD (and report via uart_handle_cts_change or 
+	uart_handle_dcd_change) the driver should indicate that the
+	signal is permanently active.
 
 	Locking: port->lock taken.
 	Interrupts: locally disabled.

  reply	other threads:[~2008-09-25 13:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 12:00 s3c24xx : TIOCM_CTS handling problem Matthieu CASTET
2008-09-25 13:14 ` Matthieu CASTET [this message]
2008-12-16 13:43 ` Matthieu CASTET
2008-12-16 14:15   ` Alan Cox
2008-12-17 13:27     ` Matthieu CASTET

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=48DB8ECA.1020302@parrot.com \
    --to=matthieu.castet@parrot.com \
    --cc=linux-serial@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).