From: Russell King <rmk+lkml@arm.linux.org.uk>
To: moreau francis <francis_moreau2000@yahoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [UART] 8250:RTS/CTS flow control issue.
Date: Thu, 17 Mar 2005 16:17:29 +0000 [thread overview]
Message-ID: <20050317161729.A12344@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050317143450.83739.qmail@web25101.mail.ukl.yahoo.com>; from francis_moreau2000@yahoo.fr on Thu, Mar 17, 2005 at 03:34:49PM +0100
On Thu, Mar 17, 2005 at 03:34:49PM +0100, moreau francis wrote:
> But why should I "degrade" my UART because some 8250
> devices have
> poor hardware implementation. Maybe we should limit
> their tx fifo to
> one byte when rts/cts flow control is enabled...
Because you don't actually understand what "hardware" and "software" flow
control refer to. It doesn't refer to the way the control is derived, as
your messages appear to imply.
What it does refer to is the *signalling* method:
* Hardware flow control is performed using the RTS and CTS signals.
These signals may be software controlled.
* Software flow control means sending an XOFF character to stop
transmission, and another character to start transmission.
In both flow control scenarios, it is very common that there may be some
latency between the reception of the "stop transmission" signal and the
transmission actually stopping.
This is precisely why the 8250 UARTs which do have "automatic flow
control" incorporated into the receiver have *large* FIFOs with
programmable trigger levels - it allows for the latency at the
transmission end.
If you want it to be immediate, then I'm afraid you're going to have a
relatively hard time, with compatibility problems with various systems.
You can't really dictate to people that they must turn off the FIFOs on
their UARTs for your product to work. (Well, you can, but _you_ would
have to support them.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-03-17 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 14:34 moreau francis
2005-03-17 16:17 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-18 9:30 moreau francis
2005-03-15 16:05 moreau francis
2005-03-17 9:57 ` Russell King
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=20050317161729.A12344@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=francis_moreau2000@yahoo.fr \
--cc=linux-kernel@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
Powered by JetHome