From: Grant Edwards <grante@visi.com>
To: linux-serial@vger.kernel.org
Subject: Re: [PATCH/RFC] 8250: Auto RS485 direction control
Date: Mon, 4 Aug 2008 16:21:10 +0000 (UTC) [thread overview]
Message-ID: <g77a9l$7ih$4@ger.gmane.org> (raw)
In-Reply-To: g779ul$7ih$1@ger.gmane.org
On 2008-08-04, Grant Edwards <grante@visi.com> wrote:
> On 2008-08-04, Laurent Pinchart <laurentp@cse-semaphore.com> wrote:
>> On Monday 04 August 2008, Tosoni wrote:
>>> About the flags names -- CARTS, UART_FCTR_RS485
>>>
>>> May I suggest CRTSTOGGLE since it is known by that kind of name in other
>>> OS's :-)
>>
>> I like Russell's proposal of sticking to CRTSCTS and adding options to setserial:
>>
>>> Should CRTSCTS be a global "enable some kind of flow control" bit and
>>> setserial be used to configure the actual flow control method
>>> (conventional RTS/CTS, DTR/DSR, alternate RTS/CTS, RS485 on RTS,
>>> RS485 on DTR) ?
>>
>> Any opinion on that ?
>
> Opposed.
>
> 1) CRTSCTS means something quite specific. Rather than
> overload that name for something unrelated, create a new
> mode bit for the new mode.
Besides, there are often times when you want _both_ RTS toggle
and CTS flow control. If both RTS toggle and RTSCTS flow
control are set, the "toggle" function would have priority
control of the RTS pin.
--
Grant Edwards grante Yow! Was my SOY LOAF left
at out in th'RAIN? It tastes
visi.com REAL GOOD!!
next prev parent reply other threads:[~2008-08-04 16:30 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 [this message]
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
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='g77a9l$7ih$4@ger.gmane.org' \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.