From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: Grant Edwards <grante@visi.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH/RFC] 8250: Auto RS485 direction control
Date: Tue, 5 Aug 2008 11:23:36 +0200 [thread overview]
Message-ID: <200808051123.39536.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <g77f8p$plq$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
On Monday 04 August 2008, Grant Edwards wrote:
> On 2008-08-04, Tosoni <jp.tosoni@acksys.fr> wrote:
>
> > Last remark:
> >
> > Interestingly, the RTS envelope on the Oxford chips is
> > implemented with... the DTR pin. On our cards we have a piece
> > of hardware which redirect the uart DTR pin to the external
> > RTS in this case.
>
> Well, that's just plain wrong. The RS-232 standard was quite
> clear that RTS is what's used to enable transmission. ;)
UARTs are not restricted to RS-232. The pin labelled RTS in the 16850 datasheet is a dual purpose pin that can be used either as RTS in RS-232 mode or as a bus direction signal in RS-485 mode.
Beside, even in RS-232 mode, RTS has at least two widely used modes. The historical usage asserts RTS when the DTE (computer) wants to send data. It then waits for the DCE (modem) to assert CTS and then sends data on the TX line. This was used with half-duplex modems. The newer flow-control usage asserts RTS when the DTE is ready to receive data. The DCE uses CTS for the same purpose in the opposite data flow direction.
This means we already have at least 3 hardware RTS/CTS modes that we need to support in the serial API.
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-05 9:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 11:47 [PATCH/RFC] 8250: Auto RS485 direction control Laurent Pinchart
2008-07-24 11:57 ` Alan Cox
2008-07-24 12:24 ` Russell King
2008-07-24 12:27 ` Alan Cox
2008-07-24 12:52 ` Russell King
2008-07-24 13:00 ` Alan Cox
2008-07-24 13:18 ` Laurent Pinchart
2008-07-24 14:13 ` Matt Schulte
2008-07-24 14:47 ` Russell King
2008-07-24 12:10 ` Russell King
2008-08-04 14:14 ` Tosoni
2008-08-04 14:22 ` Grant Edwards
2008-08-04 14:36 ` Laurent Pinchart
2008-08-04 16:15 ` Grant Edwards
2008-08-04 16:21 ` Grant Edwards
2008-08-05 9:41 ` Laurent Pinchart
2008-08-05 12:55 ` Tosoni
2008-08-06 14:30 ` Christopher Gibson
2008-08-06 16:33 ` Tosoni
2008-08-09 10:08 ` Christopher Gibson
2008-08-07 8:50 ` Laurent Pinchart
2008-08-07 13:50 ` Grant Edwards
2008-08-10 3:49 ` Christopher Gibson
2008-08-10 3:57 ` Christopher Gibson
2008-08-29 12:22 ` Christopher Gibson
2008-12-02 13:09 ` [PATCH/RFC] " Christopher Gibson
2008-12-04 11:14 ` Christopher Gibson
2008-08-04 16:47 ` [PATCH/RFC] 8250: " Tosoni
2008-08-04 17:46 ` Grant Edwards
2008-08-04 20:59 ` Matt Schulte
2008-08-05 9:23 ` Laurent Pinchart [this message]
2008-08-05 9:34 ` Tosoni
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=200808051123.39536.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=grante@visi.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