From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: Handling of automatic flow control in UART drivers
Date: Mon, 13 Oct 2014 17:09:21 +0000 (UTC) [thread overview]
Message-ID: <m1h101$tr5$1@ger.gmane.org> (raw)
In-Reply-To: 20141013144831.GA8409@jtlinux
On 2014-10-13, Johannes Thumshirn <johannes.thumshirn@men.de> wrote:
> I active the hardware auto flow control feature on the CRTSCTS flag
> in my uart_ops->set_termios() function. But then the RTS flag is set
> on every call of the uart_ops->set_mctrl() function, this seems to
> confuse the hardware.
Perhaps in that situation you should ignore the RTS setting in
set_mctrl() if CRTSCTS is enabled.
--
Grant Edwards grant.b.edwards Yow! Zippy's brain cells
at are straining to bridge
gmail.com synapses ...
next prev parent reply other threads:[~2014-10-13 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 14:48 Handling of automatic flow control in UART drivers Johannes Thumshirn
2014-10-13 17:09 ` Grant Edwards [this message]
2014-10-13 17:13 ` Peter Hurley
2014-10-14 9:22 ` Johannes Thumshirn
2014-10-14 11:18 ` Peter Hurley
2014-10-23 5:51 ` Johannes Thumshirn
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='m1h101$tr5$1@ger.gmane.org' \
--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 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).