From: "Chris Doré" <cdore@connecttech.com>
To: linux-serial@vger.kernel.org
Subject: RE: Inter-Character Delay
Date: Tue, 26 Feb 2008 15:59:41 -0500 [thread overview]
Message-ID: <010301c878ba$8365b4b0$8a311e10$@com> (raw)
In-Reply-To: <200802181336.26328.rgetz@blackfin.uclinux.org>
If I read this correctly, the summary is that you:
1. Want to add functionality to the serial driver that supports an extra
feature (the delay register).
2. Would like to know what the best way is to expose this new functionality
to a user app.
3. Are NOT looking for a way to create the delay on hardware that does not
natively support it.
I don't have good answers for you, but perhaps this will help summarize and
clear up what you are really after.
..Chris
> -----Original Message-----
> From: linux-serial-owner@vger.kernel.org [mailto:linux-serial-
> owner@vger.kernel.org] On Behalf Of Robin Getz
> Sent: February 18, 2008 1:36 PM
> To: linux-serial@vger.kernel.org
> Subject: Inter-Character Delay
>
> It is quite common on many industrial serial devices which do not support
> either software or hardware flow control to require a Inter-Character
delay
> longer than than the standard one, one and a half, or two stop bits.
>
> A device where this long inter character delay is required are devices
like
> Point of Sale terminals, and devices that are talking to Modbus (Honeywell
> SI-FTA implements a check on the inter-character gap).
>
> Some hardware manufactures have seen this need, and added it to their UART
> controllers - Atmel's AT32AP7000 has added this and called it a
"Timeguard"
> (Don't ask me why). The "timeguard delay" is controlled between 0 and 255
Bit
> Periods.
>
> http://www.atmel.com/dyn/resources/prod_documents/doc32003.pdf
>
> I think I have seen similar things for some ARM devices, and other
embedded
> architectures. Today, we have done similar things in the driver (on
hardware
> that doesn't support it natively).
>
> I'm not sure that bit periods are the best way to measure things, or
> milliseconds. I guess it really doesn't matter, as long as everyone does
it
> the same way - which brings me to my next question:
>
> Does anyone have a good idea of a standard way to expose this to
userspace?
> - grabbing 8 bits in the termios_p c_oflag isn't going to fit
> - adding a new field in the termios structure seems like overkill
> - adding backdoor ioctls for serial drivers seems like a bad idea.
>
> Thoughts?
>
> Thanks
> -Robin
> -
> To unsubscribe from this list: send the line "unsubscribe linux-serial" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-02-26 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 18:36 Inter-Character Delay Robin Getz
2008-02-26 16:11 ` Robin Getz
2008-02-26 17:11 ` Russell King
2008-02-26 18:21 ` Robin Getz
2008-02-26 19:18 ` Russell King
2008-02-26 20:10 ` Robin Getz
2008-02-26 20:59 ` Chris Doré [this message]
2008-02-27 15:57 ` Robin Getz
2008-03-03 8:29 ` 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='010301c878ba$8365b4b0$8a311e10$@com' \
--to=cdore@connecttech.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