From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Subject: API to flush rx fifo?
Date: Wed, 12 Jun 2013 20:03:50 +0000 (UTC) [thread overview]
Message-ID: <kpak75$9ko$1@ger.gmane.org> (raw)
I see the uart_ops.flush_buffer method which is used to flush the
UART's tx fifo (presumably when the user calls tcflush(TCOFLUSH)).
How does the rx fifo get flushed when the user calls tcflush(TCIFLUSH)?
--
Grant Edwards grant.b.edwards Yow! I'm shaving!!
at I'M SHAVING!!
gmail.com
next reply other threads:[~2013-06-12 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 20:03 Grant Edwards [this message]
2013-06-14 14:43 ` API to flush rx fifo? Peter Hurley
2013-06-14 15:17 ` Grant Edwards
2013-06-14 15:46 ` Peter Hurley
2013-06-14 16:29 ` Grant Edwards
2013-06-14 17:09 ` Peter Hurley
2013-06-14 17:39 ` Grant Edwards
2013-06-14 18:04 ` Peter Hurley
2013-06-14 19:12 ` Grant Edwards
2013-06-14 20:53 ` Peter Hurley
2013-06-14 18:41 ` Grant Edwards
2013-06-14 20:19 ` Peter Hurley
2014-02-26 17:14 ` Peter Hurley
2014-02-26 17:51 ` Grant Edwards
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='kpak75$9ko$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).