All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: Opening already open serial port now sets RTS and DTR?
Date: Thu, 17 Feb 2022 16:50:45 -0000 (UTC)	[thread overview]
Message-ID: <sulud5$d35$1@ciao.gmane.io> (raw)
In-Reply-To: Yg5rmQxl0AKCyez2@kroah.com

On 2022-02-17, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Thu, Feb 17, 2022 at 03:28:00PM -0000, Grant Edwards wrote:
>> It used to be that opening a serial port only set RTS and DTR if it
>> was a "first open". [...]

>> This seems to have changed, and now _every_ open sets RTS and DTR
>> even if the port was already open and RTS and DTR had already been
>> put in the desired state.
>
> When did it change?

I'm not sure. It's been a couple years since the last time I
personally used something that relied on the "old" behavior.

> Any chance you can do 'git bisect' to track it down?

Unfortunately, it would take a lot of work to get set up to do that.

I can probably try the past half-dozen or so Ubuntu distros (I'm not
sure how far back I can go with available hardware). I'll check around
with colleagues to see if we have any existing installations that are
using on the old behavior.

> And what hardware are you using here?

I've tried a couple different FTDI USB devices (FT232R single port and
FT4232H quad port). I've also tried a 16550A motherboard UART. I
believe that both FTDI and 16550 used to set RTS/DTR only on "first
open".

> Different hardware works differently in this way at times.

Which is the "expected correct" behavior?

--
Grant



      reply	other threads:[~2022-02-17 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 15:28 Opening already open serial port now sets RTS and DTR? Grant Edwards
2022-02-17 15:36 ` Greg KH
2022-02-17 16:50   ` Grant Edwards [this message]

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='sulud5$d35$1@ciao.gmane.io' \
    --to=grant.b.edwards@gmail.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.