From: claudio@evidence.eu.com
To: linux-serial@vger.kernel.org
Cc: nicolas.ferre@atmel.com, clagix@gmail.com,
Claudio Scordino <claudio@evidence.eu.com>
Subject: [PATCH 1/3] RS485: add unit of measure for delays
Date: Mon, 11 Feb 2013 16:54:24 +0100 [thread overview]
Message-ID: <1360598067-3577-2-git-send-email-claudio@evidence.eu.com> (raw)
In-Reply-To: <CAJa4H3fQ_khDVNcSu+39C+oZyc268YUgq9ahzt2ugk1_6eqYfw@mail.gmail.com>
From: Claudio Scordino <claudio@evidence.eu.com>
This patch adds the unit of measure (i.e., milliseconds) in the documentation
serial-rs485.txt (it is already available in the header file).
Signed-off-by: Claudio Scordino <claudio@evidence.eu.com>
Signed-off-by: Guido Classen <clagix@gmail.com>
---
Documentation/serial/serial-rs485.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/serial/serial-rs485.txt b/Documentation/serial/serial-rs485.txt
index 41c8378..e30335d 100644
--- a/Documentation/serial/serial-rs485.txt
+++ b/Documentation/serial/serial-rs485.txt
@@ -110,10 +110,10 @@
/* or, set logical level for RTS pin equal to 0 after sending: */
rs485conf.flags &= ~(SER_RS485_RTS_AFTER_SEND);
- /* Set rts delay before send, if needed: */
+ /* Set rts delay before send (in milliseconds) if needed: */
rs485conf.delay_rts_before_send = ...;
- /* Set rts delay after send, if needed: */
+ /* Set rts delay after send (in milliseconds) if needed: */
rs485conf.delay_rts_after_send = ...;
/* Set this flag if you want to receive data even whilst sending data */
--
1.7.9.5
next prev parent reply other threads:[~2013-02-11 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJa4H3cYT6QOaacWEy2yZjb0hM3m4p+0L2_fXBYv8tWajYkmGw@mail.gmail.com>
2013-01-30 10:30 ` RS485 implementation questions (primarly in atmel_serial.c) Claudio Scordino
[not found] ` <510A3740.6060809@evidence.eu.com>
[not found] ` <CAJa4H3dG4V6viRbVQBgHQKtJr4Sz26mkhj8-kT7RFaLGRFXW1g@mail.gmail.com>
[not found] ` <51125488.7090408@evidence.eu.com>
[not found] ` <CAJa4H3eNAS7B+aGnN0D3WJMPVtE=sxp5HhRMutq-TrBOmXb7dw@mail.gmail.com>
[not found] ` <5114B500.7050007@evidence.eu.com>
2013-02-08 12:12 ` Guido Classen
2013-02-11 15:54 ` [PATCH] atmel_serial: general fixes for RS485 and TTGR claudio
2013-02-11 17:05 ` Guido Classen
2013-02-11 15:54 ` claudio [this message]
2013-02-11 15:54 ` [PATCH 2/3] atmel_serial: use msleep for delays claudio
2013-02-11 15:54 ` [PATCH 3/3] atmel_serial: add generic TTGR support claudio
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=1360598067-3577-2-git-send-email-claudio@evidence.eu.com \
--to=claudio@evidence.eu.com \
--cc=clagix@gmail.com \
--cc=linux-serial@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
/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).