kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Implementing tight time constraints for read/write with USB serial (ftdi_sio)
Date: Tue, 4 Sep 2018 07:30:58 +0200	[thread overview]
Message-ID: <20180904053058.GB26240@kroah.com> (raw)
In-Reply-To: <CAN=42sznqK1TmQfgYGnWC6BfSV37Hchvhd6DWm4VtABuLbsiKg@mail.gmail.com>

On Mon, Sep 03, 2018 at 09:12:35PM +0200, Thomas Bracht Laumann Jespersen wrote:
> Hello all!
> 
> I'm working on a project where we want to integrate into a production line and
> listen on connected devices, and the challenge is that our setup needs to be
> fast enough.

First off, "tight time constraints" and "usb-serial" should never be in
the same sentence, unless you use the words "never will happen" in there
as well :)

There are loads of issues with trying to use USB with anything you wish
to have low-latency or determinism with, and then throw a usb-serial
device into the mix and all bets are off.  Remember there is a little
microcontroller out there at the end of the usb-serial device running a
UART and some unknown firmware blob that can take its time and do
anything it wants at any point in time, which can, and will, cause you
all sorts of headaches as you are finding out.

If you _really_ need to do something like this, use a UART attached to a
PCI card, you will have much better control and be able to actually do
what you are wanting to do here.

Good luck!

greg k-h

  parent reply	other threads:[~2018-09-04  5:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 19:12 Implementing tight time constraints for read/write with USB serial (ftdi_sio) Thomas Bracht Laumann Jespersen
2018-09-04  1:22 ` valdis.kletnieks at vt.edu
2018-09-05  9:46   ` Thomas Bracht Laumann Jespersen
2018-09-04  5:30 ` Greg KH [this message]
2018-09-05 10:25   ` Thomas Bracht Laumann Jespersen
2018-09-05 10:48     ` Greg KH
2018-09-05 11:07       ` Thomas Bracht Laumann Jespersen

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=20180904053058.GB26240@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).